Skip to Content

Summary:

Enhance SAP transactions that use Order Document Management per custom requirements. This article provides step-by-step details on how to customize ODM for specific client requirements such as adding custom fields to SAP transactions and/or documents.

Requirement:

Enhance Fixed Demand/Receipt UI – /SAPAPO/SPPFIXREQ in SPP with two new custom fields – ‘Original Qty’, ‘Ramping Indicator’. The Fixed Demand/Receipt UI utilizes ODM Framework to save the Fixed Requirements data using the standard Order Component (PFRO), Data type(PFRQ), Order Data Area(PFRQ). As its not advisable to change the standard ODM, custom ODM needs to be created and configured to meet the requirement. The custom ODM is created as a copy of the standard ODM, alongwith addition of the two new fields to meet customer requirements.

Steps to create and configure custom ODM:

1) Create custom order component ZPFQ

     – Copy standard structures and create custom table structure, table type. Include the additional custom fields per requirement.

2) Create custom order data type ZPF1

3) Create custom order data area and order document type

4) Generate and Activate the custom order component, data type, data area and document type

5) Maintain DAO initial parameters and Custom Data Access Object for Fixed requirements

Details:

Custom ODM creation and configuration for Fixed Requirements:

Step 1: SPRO transaction path

SPRO -> SCM Basis -> Order Document Management -> Configure Order Document Management

/wp-content/uploads/2012/04/aaa_95047.png

Step 2: Create Custom Order Component

Step 2.png

Step 2.1: In change mode, click on ‘New Entries’ button and maintain custom Order Component ZPFQ with the following information.

-> Create custom table structure and table type with the required fields and maintain the same in the custom order component.

Step 2.1.png

Step 2.2: Copy all the component parameters from standard Fixed Requirement Component PFRO, into custom Fixed Requirements Order Component ZPFQ.

Step 2.2.png

Step 2.3: Copy standard Order Component Index to custom Order Component, as shown below.

Step 2.3.png

Step 2.4: Copy standard Order Component Index fields to custom Order Component fields.

Step 2.4.png

Step 2.4.1.png

Step 3: Create custom Order Data Type

Step 3.1: In change mode, click on ‘New Entries’ button and maintain custom Order Data Type ZPF1, using custom Order Component created in Step 2.

Step 3.1.png

Step 3.1.1.png

Step 3.2: Copy standard Order Data Type Active Indexes to custom Order Data Type Active Indexes.

Step 3.2.png

Step 3.3: Copy standard Order data Type Access Path to custom Order Data Type Access path.

Step 3.3.png

Step 3.4: Copy standard Order Data Type Sequence and Fields in Access Path to custom Order Data Type ZPF1.

Step 3.4.png

Step 4: Create custom Order Data Area

Step 4.1: In change mode, click on ‘New Entries’ button and maintain custom Order Data Area ZPF1, using custom Order Data Type created in Step 3.

Step 4.1.png

Step 5: Maintain custom Order Document Type ZPF1 using Order Data Type created in Step 3.

Step 5.png

Step 5.1: Maintain Order Data Area assignment for Order Document Type.

Step 5.1.png

Save at the end of each step above and include all changes/customization in one transport request and use it for transporting.

Generate and Activate the custom Order Component, Data Type, Data Area and Document Type:

Step 6: SPRO transaction path for generating Order Component, Document Type and Document Area.

SPRO -> SCM Basis -> Order Document Management -> Generate Settings in Order Document Management

Step 6.png

Step 6.1: Generate Order Component

Step 6.1.png

Select ‘Generate Order Component’ and choose/enter.

Enter values as shown below and click on execute to generate custom Order Component.

Step 6.1.1.png

Step 6.2: Generate Order Data Type

Step 6.2.png

Select ‘Generate Order Data Type’ and choose/enter.

Enter values as shown below and click on execute to generate custom Order Data Type.

Step 6.2.1.png

Step 6.3: Generate Order Data Area

Step 6.3.png

Select ‘Generate Order Data Area’ and choose/enter.

Enter values as shown below and click on execute to generate custom Order Data Area.

Step 6.3.1.png

Step 7: SPRO transaction path for activating Order Component, Document Type and Document Area.

SPRO -> SCM Basis -> Order Document Management -> Activate Settings in Order Document Management

Step 7.png

Step 7.1: Activate Order Component

Step 7.1.png

Select ‘Activate Order Component’ and choose/enter.

Enter values as shown below and click on execute to activate custom Order Component.

Step 7.1.1.png

Step 7.2: Activate Order Data Type

Step 7.2.png

Select ‘Activate Order Data Type’ and choose/enter.

Enter values as shown below and click on execute to activate custom Order Data Type.

Step 7.2.1.png

Step 7.3: Activate Order Data Area

Step 7.3.png

Select ‘Activate Order Data Area’ and choose/enter.

Enter values as shown below and click on execute to activate custom Order Data Area.

Step 7.3.1.png

Maintain DAO initial parameters and custom Data Access Object for Fixed Requirements:

Step 8: Maintain DAO Initial Parameters and custom Data Access Object for fixed requirements.

Go to transaction “/SCMB/TDL_CUST_CFG” and click on new entries button to maintain DAO Initial Parameters for fixed requirements

Step 8.png

Step 9: Assign custom DAO class for fixed requirements

Copy standard DAO class “/SCMB/CL_TDL_ODM_FR_DAO” for fixed requirements to a custom DAO class and make relevant changes to read the correct custom Order Document Type and Order Component.

Go to transaction “/SCMB/TDL_CUST_CFG” and replace standard DAO class for fixed requirements.

Step 9.png

Note: SAP generates two new tables to hold the Fixed Requirements data – /1OM/ZPF1ZPFQ210(history table) & /1OT/ZPF1ZPFQ210(tracking table, holds current active data). The last three characters of the table name is dependent on the SAP client number of the system, hence would vary in each environment. The structure of these tables is driven by the custom data structure and table type mentioned in Step 2.1.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply