Hierarchy
⤷ PSM-GM-GTE (Application Component) Grantee Management
⤷ GMBASIS_E (Package) Grants management (basis)
IMG Activity
ID | SIMG_GM_BADI_SDORDER | BAdI: Map Grant Master Data to Sales Order |
Transaction Code | S_PLN_62000227 | (empty) |
Created on | 20040224 | |
Customizing Attributes | SIMG_GM_BADI_SDORDER | BAdI: Map Grant Master Data to Sales Order |
Customizing Activity | SIMG_GM_BADI_SDORDER | BAdI: Map Grant Master Data to Sales Order |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | GM_SALES_ORDER_EXT |
Use
When a grant is changed to status "Award" or created as an award, a sales order is created simultaneously, provided a non-manual billing rule is maintained in the grant.
The implementation of this Business Add-In (BAdI)I makes it possible to map grant master data to the sales order.
The import parameter I_GMGR_FIELDS represent the data contained in the grant master table GMGR, including the Customer Include.
The export parameter E_EXTENSIONIN is the extension table for BAPIs and should be filled with the sales order data that reflects the grant master data.
The export parameter E_RETURN is the error messages table for BAPIs and should be filled with any error messages that arise within the implementation of the BAdI.
Requirements
You are using Grants Management (GM) and want to create grants relevant for billing. However, you want to map some grant master data to sales order data.
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:
- In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
- Enter a short text for the implementation in the Short text for implementation field.
- From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20040224 |
SAP Release Created in | 500 |