Hierarchy

⤷

⤷

IMG Activity
ID | SIMG_FM_ONLINE_ASST | BAdI: Field Status for FM Account Assignment for Orders |
Transaction Code | S_ALN_01002513 | (empty) |
Created on | 20031215 | |
Customizing Attributes | SIMG_FM_ONLINE_ASST | BAdI: Field Status for FM Account Assignment for Orders |
Customizing Activity | SIMG_FM_ONLINE_ASST | BAdI: Field Status for FM Account Assignment for Orders |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FM_ONLINE_ASSIGNMENT |
Use
SAP provides the BAdI definition FM_ONLINE_ASSIGNMENT and methods that enable further customizing of field status for the FM objetcs used in the online order assignments (Sales Distribution, Plant Maintenance, Network, and Network Activity). For each order type you must create an implementation using the following predefined methods:
- Method GET_FIELD_STATUS_SD - Order type Sales Distribution
- Method GET_FIELD_STATUS_PM - Order Type Plant Maintenance
- Method GET_FIELD_STATUS_NP - Order Type Network
- Method GET_FIELD_STATUS_NV - Order Type Network Activity
SAP provides the BAdI definition FM_ONLINE_ASSIGNMENT and the following methods that enable to copy aditional values from the online order (Sales Distribution, Plant Maintenance, Network, and Network Activity) to be used in the determination of the default FM Account Assignment:
- Method SD_DATA_COPY_TO_COBL - Copy SD Order Data to the structure COBL
- Method PM_DATA_COPY_TO_COBL - Copy PM Order Data to the structure COBL
- Method NP_DATA_COPY_TO_COBL - Copy NP Order Data to the structure COBL
- Method NV_DATA_COPY_TO_COBL - Copy NV Order Data to the structure COBL
Requirements
The FM integration to online orders must be active.
Standard settings
We do not deliver any standard settings.
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 | 257 | Create User Exits |
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 | 20050113 |
SAP Release Created in | 500 |