EHP4 for SAP ERP
6.0
September 2010
English
Logistic General (SD &
MM) Delta for SCPV (467)
Building Block Configuration Guide
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
Copyright
© Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components
of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,
OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,
POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System
Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM
Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C ®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented
and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP
products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and
in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its
affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
© SAP AG
Page 2 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
Icons
Icon
Meaning
Caution
Example
Note or Tip
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Typographic Conventions
Type Style Description
Example text Words or characters that appear on the screen. These include field names,
screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation.
Example
text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE
TEXT
Names of elements in the system. These include report names, program
names, transaction codes, table names, and individual key words of a
programming language, when surrounded by body text, for example, SELECT
and INCLUDE.
Example
text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as names
of installation, upgrade and database tools.
EXAMPLE TEXT Keys
on the keyboard, for example, function keys (such as F2) or the ENTER
key.
Example
text
Exact user entry. These are words or characters that you enter in the system
exactly as they appear in the documentation.
<Example
text>
Variable user entry. Pointed brackets indicate that you replace these words
and characters with appropriate entries.
© SAP AG
Page 3 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
Contents
Logistic General (SD & MM) Delta for SCPV .................................................................................. 5
1
Purpose .................................................................................................................................... 5
2
Preparation ............................................................................................................................... 5
2.1
3
Prerequisites .................................................................................................................. 5
Configuration ............................................................................................................................ 5
3.1
Sales and Distribution .................................................................................................... 5
3.1.1
Maintaining Item Categories: All Parameters ............................................................ 5
3.1.2
Defining Item Category Groups ................................................................................. 7
3.1.3
Assigning Item Categories ......................................................................................... 7
3.1.4
Assigning Schedule Line Categories ......................................................................... 8
3.1.5
Defining Copy Control for Sales Documents ............................................................. 8
3.1.6
Defining Item Categories for Deliveries ..................................................................... 9
3.1.7
Defining Item Category Determination in Deliveries ................................................ 10
3.1.8
Maintaining Copying Control for Deliveries - Item ................................................... 11
3.1.9
Maintaining Copying Control for Billing Documents ................................................ 11
3.1.10
Assigning Value Fields............................................................................................. 12
3.1.11
Defining Requirements Classes .............................................................................. 13
3.1.12
Defining Requirement Types ................................................................................... 14
3.1.13
Determining Requirement Types ............................................................................. 14
3.2
3.2.1
Logistic General ........................................................................................................... 15
Defining Product Hierarchies ................................................................................... 15
3.3
Defining Screen Layout for Purchasing Info Records .................................................. 16
3.4
Implementing BAdi for Purchasing Documents Processing ........................................ 17
© SAP AG
Page 4 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
Logistic General (SD & MM) Delta for SCPV
1 Purpose
This configuration guide provides you with the information you need to set up the configuration of
this building block manually.
If you do not want to configure manually and prefer an automated installation process using BC
Sets and other tools, refer to the Quick Guide that is located on SAP Note 1497537.
2 Preparation
2.1
Prerequisites
Before you start installing this building block, you must install prerequisite building blocks. For
more information, see the building block prerequisite matrix located on the Documentation DVD
on the Content Library page under Technical Information (on the left navigation pane).
3 Configuration
3.1
Sales and Distribution
3.1.1 Maintaining Item Categories: All Parameters
Use
The item categories influence price determination and the transfer of requirements, among other
things.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
SPRO
IMG menu
Sales and Distribution  Sales  Sales Documents  Sales
Document Item  Define Item Categories
2. On the Change View Maintain Item Categories: Overview screen, choose New Entries.
3. Make the following entries:
Field name
User action and
values
Note
Item Category
YHGC
Config.at Mat.Level
Business Item
X
Yes
© SAP AG
Page 5 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
Field name
User action and
values
Note
Sched. Line Allowed
X
Yes
Completion Rule
B
Item is completed after full quantity has
been referenced
Wgth/Vol.relevant
X
Yes
Pricing
X
Item is pricing relevant
Determine Cost
X
Stock value is calculated during pricing
Incompletion Proced.
20
Standard Item
PartnerDetermProced.
N
Standard Item
Screen Seq.Grp
N
TextDetermProcedure
01
Sales Item
Config. Strategy
01
Sales Order Strategy (TAC, TAM)
Structure scope
D
Configuration, poss. With BOM explosion
Variant Matching
X
Yes
Item Category
YHTC
Config.at Mat.Level
Business Item
X
Yes
Sched. Line Allowed
X
Yes
Item Relev.for Dlv
X
Yes
Billing Relevance
A
Delivery related billing document
Wgth/Vol.relevant
X
Yes
Pricing
X
Item is pricing relevant
Determine Cost
X
Stock value is calculated during pricing
Incompletion Proced.
20
Standard Item
PartnerDetermProced.
N
Standard Item
Screen Seq.Grp
N
Standard Item
TextDetermProcedure
01
Sales Item
Item Cat.Stats.Group
1
Order, Debit Memo
Config. Strategy
01
Sales Order Strategy (TAC, TAM)
Structure scope
D
Configuration, poss. With BOM explosion
Variant Matching
X
Yes
© SAP AG
Page 6 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
4. Choose Save.
3.1.2 Defining Item Category Groups
Use
You need the item category group to determine item categories.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
SPRO
IMG menu
Sales and Distribution  Sales  Sales Documents  Sales
Document Item  Define Item Category Groups
2. On the Change View Materials: Item Category Groups in Material Master: Overview screen,
choose New Entries.
3. Make the following entries:
Field name
User action and values
Note
ItCGr
YHC1
Configuration
4. Choose Save.
3.1.3 Assigning Item Categories
Use
In this step, you assign the item categories. The item category assigned depends on the sales
document type and the item category group of the material, among other things.
Prerequisites
Definition of sales document types, item categories, and item category group as described above.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
SPRO
IMG menu
Sales and Distribution  Sales  Sales Documents  Sales
Document Item  Assign Item Categories
2. On the Change View Item Category Assignment: Overview screen, choose New entries.
3. Make the following entries:
Field name
User action and values
User action and values
Sales Doc.Type
QT
OR
Item cat.group
YHC1
YHC1
Item category
YHGC
YHTC
© SAP AG
Page 7 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
Field name
User action and values
Manual item cat
AGN
User action and values
4. Choose Save.
3.1.4 Assigning Schedule Line Categories
Use
In this step, you assign schedule line categories to the defined item categories. You do not need
to define schedule line categories, since you can use the standard schedule line category CP.
Prerequisites
Definition of item categories as described above.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
SPRO
IMG menu
Sales and Distribution  Sales  Sales Documents  Schedule Lines
 Assign Schedule Line Categories
2. On the Change View Assign Schedule Line Categories: Overview screen, choose New
entries.
3. Make the following assignments:
Field name
User action and values
User action and values
Item Category
YHTC
YHTC
Typ
ND
PropSchdLneCat.
CP
CN
4. Choose Save.
3.1.5 Defining Copy Control for Sales Documents
Use
In this step, you define the copy control for sales documents to the delivery.
Prerequisites
The standard order type OR and the item category YHCG have been created.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
VTAA
IMG menu
Sales and Distribution  Sales  Maintain Copy Control for Sales
© SAP AG
Page 8 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
Documents  Copying Control: Sales Document to Sales Document
2. In the Choose Activity box, double-click Copying Control: Sales Document to Sales
Document.
3. On the Display View Header: Overview screen, choose Display Change.
4. To create a new entry for the copy control, choose New Entries.
5. Make the following entries:
Field name
User action and values
Note
Target sls doc. type
OR
Standard order
From SalesDoc Type
QT
Quotation
DataT (VBAK)
051
DataT (VBKD)
101
DataT (VBPA)
001
Copying requirements
001
6. Double-click the Item folder in the dialog structure pane.
7. Choose New Entries.
8. Make the following entries:
Field name
User action and values
Note
Item Category
YHGC
Standard Item
ItemCat Proposal
YHTC
DataT (VBAP)
151
DataT (VBKD)
102
DataT (VBPA)
002
FPLA
251
Copying requirements
301
Copy schedule lines
X
Update document flow
X
Pricing type
A
Pos./neg. quantity
+
Reexplode structure/free goods
X
9. Choose Save.
10. Choose Back.
3.1.6 Defining Item Categories for Deliveries
Use
In this step, you assign the item category YHTC to the delivery item categories.
© SAP AG
Page 9 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
Prerequisites
The item category YHTC exists.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
0VLP
IMG menu
Logistics Execution  Shipping  Deliveries  Define Item
Categories for Deliveries
2. On the Change View Delivery item categories: Overview screen, choose New Entries.
3. On the New Entries: Details of Added Entries screen, enter the following values:
Field name
Description
User action and values
Item Category
YHTC
Document cat.
J (Delivery)
Relevant for picking
Select
AutoBatchDeterm
Select
Note
4. Choose Save.
3.1.7 Defining Item Category Determination in Deliveries
Use
In this step, you assign the item category group YHC1 to the delivery item category.
Prerequisites
The item category YHTC exists.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
0184
IMG menu
Logistics Execution  Shipping  Deliveries  Define Item
Categories Determination in Deliveries
2. On the Change View Delivery item categories determination: Overview screen, choose New
Entries.
3. On the New Entries: Overview of Added Entries screen, enter the following values:
DlvT
ItCG
LF
YHC1
LF
YHC1
CHSP
YB99
LB
NORM
V
LBN
© SAP AG
Usg.
ItmC
TAN
Page 10 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
4. Choose Save.
3.1.8 Maintaining Copying Control for Deliveries - Item
Use
To create delivery documents with reference to a sales order, you must define the copying
control.
Prerequisites
The definition of delivery item categories, as described above.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
VTLA
IMG menu
Logistics Execution  Shipping  Copying Control  Specify Copy
Control for Deliveries
2. On the Display View Header: Overview screen, select the row with Tgt LF and Source OR
and double-click Item in the Dialog Structure pane.
3. Choose Display  Change.
4. Choose New Entries.
5. On the New Entries: Details of Added Entries screen, make the following entries:
Field name
Description
User action and values
Item Category
YHTC
Order requirements
101
Item data
101
Item Ext. System
0
Business data
2
Update document flow
X
Pos./neg. quantity
+
Note
6. Choose Save.
3.1.9 Maintaining Copying Control for Billing Documents
Use
To create billing documents with reference to a sales order, you must define the copying control.
Prerequisites
The definition of sales document types and item categories, as described above
Procedure
© SAP AG
Page 11 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
1. Access the activity using one of the following navigation options:
Transaction
code
VTFL
IMG menu
Sales and Distribution  Billing  Billing Documents  Maintain
Copying Control For Billing Documents  Copying control: Delivery
document to billing document
2. On the Display View Header: Overview screen, select the row with Tgt F2 and Source LF and
double-click Item in the Dialog Structure pane.
3. Choose Display  Change.
4. Choose New Entries.
5. On the New Entries: Details of Added Entries screen, make the following entries:
Field name
Description
User action and values
Item Category
YHTC
Copying requirements
004
Data VBRK/VBRP
001
Billing quantity
G
Pos./neg. quantity
+
Pricing type
G
Note
6. Choose Save.
3.1.10 Assigning Value Fields
Use
To assignment of SD condition VA00 to Value Fields in the Operation concern.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
KE4I
IMG menu
Controlling  Profitability Analysis  Flows of Actual Values  Transfer
of Incoming Sales Orders  Assign Value Fields  Maintain
Assignment of SD Condition to CO-PA Value Fields
2. Select your Operating concern and choose New Entries.
3. Make the following entries:
OpCo
CTyp
Name
Val. fld
Description
XXXX
VA00
Variant Price
ERLOS
Revenue
© SAP AG
Transfer +/-
Page 12 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
4. Choose Save.
3.1.11 Defining Requirements Classes
Use
The purpose of this activity is to define and maintain the requirement classes with which you
control all functions relevant to requirements in logistics. Then you have to check the requirement
classes to make sure that they meet the requirements of Cost Object Controlling. Then in the next
step you have to adapt the parameters in the requirements class that are relevant to cost
accounting.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
OVZG
IMG menu
Sales and Distribution  Basic Functions Availability Check and
Transfer of Requirements  Transfer of Requirements Define
Requirements Classes
2. Select requirement class YB7 and copy it to YHT.
Field name
Description
YHT
MTO val. w/o RA
User action and values
Note
MTOw/o RA
3. Choose Save.
4. Check the requirements class with the following navigation options:
Transaction
code
SPRO
IMG menu
Controlling  Product Cost Controlling  Cost Object Controlling 
Product Cost by Sales Order  Control of Sales-Order-Related
Production/Product Cost by Sales Order Check Requirements Classes
5. On the Change View Requirements Class for Costing and Account Assignment Overview
screen, select the following entry
Field name
Description
YHT
MTO val. w/o RA
User action and values
Note
MTO w/o RA
6. Choose Details.
7. Make the following entries:
Field name
Description
User action and values
Note
Costing
Costing
X
Costing ID
B
Costing Method
1
© SAP AG
Page 13 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
Costing Variant
YHSC
Costing Sheet
Blank (delete entry)
Assembly/Requirements
Assembly type
No changes
Account assignment
Acc. Assignment Cat.
M (check)
Valuation
M (check)
Leave the remaining fields blank.
8. Choose Save.
3.1.12 Defining Requirement Types
Use
The requirements type determines the planning strategy to be used for a particular requirement.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
OVZH
IMG menu
Controlling  Product Cost Controlling  Cost Object Controlling 
Product Cost by Sales Order  Control of Sales-Order-Related
Production/Product Cost by Sales Order  Check Requirements Types
2. On the Change View Requirements Types: Overview screen, make the following entries for
requirements type YKEK:
Field name
Description
User action and values
RqTy
Requirements type
YHT
ReqCl
Requirement class
YHT
Note
3. Choose Save.
3.1.13 Determining Requirement Types
Use
You have to define a requirement type for each item category defined. The requirement type is
used to determine several actions in further processing, for example, transfer requirements to
planning and perform ATP check.
Prerequisites
The definition of item categories as described previously.
Procedure
© SAP AG
Page 14 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
1. Access the activity using one of the following navigation options:
Transaction
code
SPRO
IMG menu
Sales and Distribution  Basic Functions  Availability Check and
Transfer of Requirements  Transfer of Requirements  Determination
Of Requirement Types Using Transaction
2. On the Change View Assignment of Requirement Types to Transaction: Overview screen,
make the following entries:
ItCa
Typ
YHTC
Q
1
YHTC
ND
1
3. Choose Save.
3.2
Logistic General
3.2.1 Defining Product Hierarchies
Use
The purpose of this activity is to create product hierarchies for Photovoltaic and Semiconductor
materials.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
OVSV
IMG menu
Logistics - General  Material Master  Settings for Key Fields 
Data Relevant to Sales and Distribution  Define Product Hierarchies
2. On the Customizing Product Hierarchy screen, select Maintenance: Prod.Hier. and choose
Details.
3. On the Change View Materials: Product Hierarchies: Overview screen, choose New Entries.
4. Make the following entries:
Product Hierarchy
Description
00001
Best Practices Prod. Hier. Top Level
00001H0001
Photovoltaic
00001H000100000001
Solar Modules
00001H0002
Semiconductor
00001H00020000002
Semiconductor Devices
© SAP AG
Page 15 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
5. Choose Enter.
6. Save your entries.
7. Return to the SAP Easy Access Menu.
Result
Product Hierarchies have been created.
3.3
Defining Screen Layout for Purchasing Info
Records
Use
The purpose of this activity is to maintain the settings for the screen layout and field attributes of
purchasing info records.
Procedure
1. Access the activity using one of the following navigation options:
Transaction
code
SPRO
IMG menu
Materials Management  Purchasing  Purchasing Info Record 
Define Screen Layout
2. On the Change View “Screen Layout: Info Record”: Overview screen, select the entry ME11
Create Purchasing Info Record and choose Details.
3. On the Maintain Table 162: Field Selection Groups screen, select the entry Administration
Data and choose Details.
4. On the Maintain Table 162: Field for Field Selection Group screen, make the following
entries:
Field Label
Timely Consumption
© SAP AG
Reqd. entry
Opt. entry
Display
X
Page 16 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
5. Save your entries
6. Repeat steps 2 to 5 for the field selections ME12 – Change purchasing info record and ME13
– Display purchasing info record.
7. Go back to the SAP Easy Access screen.
Result
You have maintained the field selection for purchasing info records
3.4
Implementing BAdi for Purchasing Documents
Processing
Use
The BAdI PP_OM_BD_BANF_HEADER_MATERIAL - Define Purchase Requisition Header
Material is used to fill the material field in the purchase requisition item if a purchase requisition is
created by an externally processed operation. This enables you to also transfer the configuration
data.
This material then appears in the external processing data of the routing or recipe.
The description of the purchase requisition item is not changed.
Allow the assignment of a material info record with a material number to an external processing
operation in a production order. The assignment is required for the enhanced outsourced
manufacturing process.
Procedure
1. Access the activity using one of the following navigation options:
SAP ECC menu
Tools  ABAP Workbench  Utilities  Business Add-Ins 
Implementation
Transaction
code
SE19
2. On the BAdI Builder: Initial Screen for Implementations screen, in the Edit Implementation
area, choose New BAdI and enter the Enhancement Implementation
YD249_PP_OM_BI_BANF_HEADER_MAT.
3. Choose Display to check if the enhancement exists.
If this enhancement exists, execute steps 4 ~ 8 to modify it.
If this enhancement not exist, execute steps 9 ~ 21 to create it.
4. On the Enhancement Implementation YD249_PP_OM_BI_BANF_HEADER_MAT Display
screen, choose the implementing class in the navigation area on the left side by expanding
the navigation tree and double-clicking Implementing Class.
5. Double-click the method IF_PP_OM_BANF_HEADER_MATERIAL~GET_BANF_MATERIAL.
6. On the Class Builder: Class YD249_CL_OM_BI_BANF_HEADER_MAT Display screen,
choose Display <-> Change.
7. Replace the row 52 entry check: i_material = 'F249'.
with the following code
© SAP AG
Page 17 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
check: i_material = 'F249' OR i_material = 'HT-F411-1'.
8. Activate the BAdI Implementation. Do not process the rest of this activity.
9. On the BAdI Builder: Initial Screen for Implementations screen, in the Create Implementation
area, choose New BAdI and enter the enhancement spot PP_OM_ES_BANF.
10. Choose Create Impl.
11. On the Create Enhancement Implementation dialog box, make the following entries:
Field name
User action and values
Enhancement Implementation
YD249_PP_OM_BI_BANF_HEADER_MAT
Description
YD249- Enhancement Outsourced Manufacturing
12. Choose Creation of Enhancement.
13. Enter your development package, for example Z001, and choose Save.
14. On the Prompt for transportable Workbench request dialog box, enter a transport request and
choose Continue.
15. On the Enhancement Implementation YD249_PP_OM_BI_BANF_HEADER_MAT: Create
BAdI dialog box, make the following entries:
Field name
User action and values
BAdI Implementation
YD249_IM_OM_BI_BANF_HEADER_MAT
Description
Implementation: Define Purchase Requisition Header Material
Implementation Class
YD249_CL_OM_BI_BANF_HEADER_MAT
BAdI Definition
PP_OM_BD_BANF_HEADER_MATERIAL
16. Confirm your entries.
17. On the Enhancement Implementation YD249_PP_OM_BI_BANF_HEADER_MAT screen,
choose the implementing class in the navigation area on the left side by expanding the
navigation tree and double-clicking Implementing Class.
18. Double-click the method IF_PP_OM_BANF_HEADER_MATERIAL~GET_BANF_MATERIAL.
19. Confirm the Create Method Implementation dialog box.
20. On the Class Builder: Class YD249_CL_OM_BI_BANF_HEADER_MAT screen, copy the
following code:
method IF_PP_OM_BANF_HEADER_MATERIAL~GET_BANF_MATERIAL.
*********************************************************************
*
*
* This implementation transfers the order header material or its
*
* reference material to the purchase requisition.
*
*
*
* The reference material is taken if it is maintained in the
*
* material master of the order header material and if the control *
* key is set to WIP mandatory.
*
*
*
* If the order header material is taken, its configuration is also *
* transfered to the purchase requisition
*
*
*
*********************************************************************
DATA: ls_t430
© SAP AG
TYPE t430,
Page 18 of 20
SAP Best Practices
ls_marc
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
TYPE marc.
* A material must be provided
CHECK i_material IS NOT INITIAL AND
i_plant
IS NOT INITIAL.
* For operations refering to a standard routing
* a material makes sense only if there is no purchase
* info record (which would never refer to a material)
IF is_operation-plnty = 'S' AND
is_operation-infnr IS NOT INITIAL.
EXIT.
ENDIF.
* Get details of control key
CALL FUNCTION 'CO_TA_T430_READ'
EXPORTING
steus
= is_operation-steus
IMPORTING
struct
= ls_t430
EXCEPTIONS
no_entry = 1
OTHERS
= 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE 'E' NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
* Operation must be external
CHECK ls_t430-lief IS NOT INITIAL.
*
*
*
*
*
*
SAP BP for Discrete Manufacturing V1.604:
Implementation is only valid for BP-DM-Scenario 249 material F249 &
BP-HT-SCPV-Scenario 452 material HT-F411-1,
otherwise the implementation causes an error when the info record
has no material.
temporary solution, because we can't use the implementation of
* client 002
check: i_material = 'F249' OR i_material = 'HT-F411-1'.
* Determine reference material if WIP is mandatory
* for this control key
IF ls_t430-wip = '1'.
CALL FUNCTION 'MARC_SINGLE_READ'
EXPORTING
matnr
= i_material
werks
= i_plant
IMPORTING
wmarc
= ls_marc
EXCEPTIONS
lock_on_marc
= 1
lock_system_error = 2
wrong_call
= 3
not_found
= 4
OTHERS
= 5.
© SAP AG
Page 19 of 20
SAP Best Practices
Logistic General (SD & MM) Delta for SCPV (467): Configuration Guide
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE 'E' NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDIF.
* Transfer material to BANF header
IF ls_marc-ucmat IS NOT INITIAL.
*
Reference material
c_matnr = ls_marc-ucmat.
ELSE.
*
Order header material
c_matnr = i_material.
ENDIF.
* Transfer configuration to BANF header
c_cuobj = i_order_material_configuration.
endmethod.
21. Activate the BAdI Implementation.
© SAP AG
Page 20 of 20