Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
PP-SFC (Application Component) Production Orders⤷
COWIPB (Package) WIP Batch
IMG Activity
| ID | CO_WIPB_CHG_CLSF | BAdI: Change/Calculate on Basis of Characteristics Classification |
| Transaction Code | S_E4A_94000147 | (empty) |
| Created on | 20080506 | |
| Customizing Attributes | CO_WIPB_CHG_CLSF | BAdI: Change/Calculate on Basis of Characteristics Classification |
| Customizing Activity | CO_WIPB_CHG_CLSF | BAdI: Change/Calculate on Basis of Characteristics Classification |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | CO_WIPB_CHG_CLSF |
Use
You can use the Business Add-In (BAdI) CO_WIPB_CHG_CLSF to propose or change valuations for individual characteristics in the transactions Enter Time Ticket for Production Order or Enter Time Ticket for Process Order (CO11N and COR6N respectively, in brief: the confirmation transactions). In addition, you have the opportunity to influence system behavior in dependence on the characteristic values of WIP or goods receipt batches.
Typical applications for this BAdI include the following:
- Generation of default values for batch characteristics (e.g. depending on material, material group etc.)
- Postprocessing of existing characteristic valuations
- Various calculations and evaluations on the basis of characteristic values upon each PAI of the confirmation transaction
The BAdI is invoked by the function module CO_WIPB_SET_CLSF_CUST in the case of the following functions:
- Creation of WIP or goods receipt batch
- Changing of classification of a WIP or goods receipt batch (in the confirmation transaction)
- Classification of the goods receipt batch in the Goods Movements transaction (MIGO)
Requirements
Knowledge of ABAP-OO is advantageous for the implementation of this BAdI
Standard settings
- In the standard system, the BAdI is not active.
- The BAdI can be used multiple times.
- The BAdI is filter-independent.
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 |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | CO_WIPB_CHG_CLSF | 0 | HLA0009525 O HLA0009761 |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20080827 |
| SAP Release Created in | 604 |
