Hierarchy
⤷ LO-AB (Application Component) Agency Business (Global Trade)
⤷ WZRE (Package) Agency Business
IMG Activity
ID | WLF_PAOBJNR | BAdI: Extension Profitability Segment |
Transaction Code | S_E38_98000122 | (empty) |
Created on | 20070824 | |
Customizing Attributes | WLF_PAOBJNR | BAdI: Profitability Segment Determination |
Customizing Activity | WLF_PAOBJNR | BAdI: Extension Profitability Segment |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | WLF_PAOBJNR |
Use
You can use this Business Add-In to implement your own mapping for profitability segment determination.
The profitability segment determination determines a separate <DS DSYS Reference (SO70 link)>PAOBJNR (Number for Profitability Segments). When you post the item in accounting, this number is transferred and used to assign the item to the profitability segment. If several items are assigned to the same profitability segment, you still have different profitability segment numbers (PAOBJNR) in the agency document. As a result, the data being transferred to accounting cannot be summarized beforehand in the agency system, leading to long runtimes when documents contain a large number of items.
You can use this Business Add-In to allocate items that are assigned to the same profitability segment to an identical profitability segment number (PAOBJNR) in the agency document. This way, in method <DS:IO.IF_EX_WLF_ACC_ENHANCEMENT CHANGE_AFTER_SUMMARIZATION>CHANGE_AFTER_SUMMARIZATION des BAdIs <DS DSYS Reference (SO70 link)> WLF_ACC_ENHANCEMENT you can summarize the ACCIT lines before calling the accounting interface (function module AC_DOCUMENT_CREATE) and achieve significant run time improvements.
Requirements
Standard settings
The Business Add-In is not active in the standard system.
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 | 3 | Nonrequired activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | WLF_PAOBJNR | 0 | ALR0000097 | Agency Business (Global Trade) |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20070824 |
SAP Release Created in |