Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-MP-NF (Application Component) Non-Ferrous Metal enhancements⤷
/NFM/CA (Package) NF Metal Processing: Cross-Application
IMG Activity
| ID | /NFM/IMG_MM_CA_BADI | BAdI: Changes to Document Data of NF Metal Processing |
| Transaction Code | /NFM/12001214 | (empty) |
| Created on | 20021106 | |
| Customizing Attributes | /NFM/IMG_MM_CA_BADI | BAdI: Changes to Document Data of NF Metal Processing |
| Customizing Activity | /NFM/IMG_MM_CA_BADI | BAdI: Changes to Document Data of NF Metal Processing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /NFM/ORDERPOS_DATA |
Use
This Business Add-In (BAdI) is used in the component Enhancements:Non-Ferrous Metal (IS-MP-NF).
The BAdI /NFM/ORDERPOS_DATA provides various methods for handling NF metal data in documents. You can, for example, change the default NF data proposed or pass the NF data to your own programs prior to updating. More information is given in the documentation for the individual methods (see below).
Requirements
NF metal processing must be activated in Customizing of NF Metal Processing -> NF Cross-Application Components -> Maintain Basic Settings for NF Metal Processing .
Standard settings
The Business Add-In is not active in the standard system. There is no default implementation.
The Business Add-In permits multiple use. All active implementations are called and executed.
The BAdI uses the NF document type as filter; the following values are possible:
A: Sales document
B: Purchasing document
F: Billing document
R: Invoice
N: Cancellation
Activities
You must create an active implementation in order to activate the Business Add-In.
When you call the IMG activity, you are first taken to a dialog window in which you enter a name for the implementation.
If implementations have already been created for this BAdI, you are taken to a dialog window in which the existing implementations are displayed. Choose Create in this window and proceed as follows:
- Enter a name for the implementation of the BAdI in the Implementation field and then choose Create.
- You are taken to the initial screen for creating BAdi implementations.
- In this screen enter a short text for the implementation in the Short text for implementation field.
- Choose the Interface tab index.
On this index tab the Name of Implementing Class field is automatically filled because the system assigns a class name based on the name of your implementation.
- Save your input and make an assignment to a package.
- Double-click on the class and activate the class in this screen.
- Position the cursor on a method and double-click to go to method processing.
- Enter the desired implementation coding between the statements
method <Interface-Name>~<Name of Method>.andendmethod.. - Save and activate your coding and navigate back to the Change Implementation screen.
- Perform a save in the Change Implementation screen.
Note: It is also possible to first create an implementation for a BAdI and to activate it later. If this is what you want to do, terminate processing at this point.
- Choose Activate..
When the application program is executed, the coding you saved in the method is executed.
See also:
- Method CREATE: Changing the Proposed NF Data
- Method SAVE_INVOICE: NF Data for Invoice before Saving
- Method SAVE_PURCHASE_ORDER: NF Data for Purchase Order before Saving
- Method SOLD_TO_UPDATE: Reaction to Change of Sold-To Party in Batch Input
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20021106 |
| SAP Release Created in | 471 |
