Costing: BAdI for valuation of external processing

[] [] [] [] [] [] [] [] [] [] [] []

  1. Costing: BAdI for valuation of subcontractingSymptom In the costing, you can use a relevant purchasing info record only to valuate a costing item of the “subcontracting” type. A BAdI or user exit does not exist. Other terms...
  2. CK40N: Unnecessary memory allocation for BAdI implementationSymptom You are experiencing higher memory consumption during processing of steps ‘Selection’, ‘Structure Explosion’ and ‘Costing’ of a costing run after introduction of BAdI MAT_SELECTION_CK (see note 1019389). In the worst case,...
  3. Incorrect account in sales order costingSymptom In the sales order costing, the system determines an incorrect account for the subcontracting item. The system executes the account determination with the activity “GBB”. The system should execute the account...
  4. Incorrect account in sales order costingSymptom In the sales order costing, the system determines an incorrect account for the subcontracting item. The system executes the account determination with the activity “GBB”. The system should execute the account...
  5. System issues message CK 869 in the mixed costingSymptom In the context of a cost estimate with quantity structure, you carry out a mixed costing. When you display the itemizations for the various cost component views, the system issues message...
  6. Costing: Price unit incorrect for change of plantSymptom An itemization of a costing contains the incorrect price unit or the material origin and/or the origin group is incorrect. Another symptom: You use transaction CK13 to view the costed multilevel...
  7. Sales order costing: material variant costed incorrectlySymptom In sales order costing the costing structure contains a material with special procurement key ‘production in other plant’. The material is a ‘material variant’ (configured material) in the other plant. During...

Symptom

In the costing, you can use a relevant purchasing info record only to valuate a costing item of the “external processing” type. A BAdI or user exit does not exist.

Other terms

CK11N, CK40N, VA01, VA02, CKUC, CK74N, KKE1, CKECP
Reason and Prerequisites

There is a problem in the program design.
Solution

Implement the program corrections by importing the relevant Support Package, or for Basis Release 700 and a minimum of SAPKB70009 use transaction SNOTE.
When you implement these corrections, the system creates the BAdI EXTERNAL_OPERATION_VAL_CK in the enhancement spot MATERIAL_VALUATION_CK. The method GET_PRICE can then be used to valuate external processing items in the costing. The BAdI documentation contains a description.

————————————————————————
|Manual Post-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_APPL SAP Application |
| Release 600 Until SAPKH60015 |
| Release 602 Until SAPKH60205 |
| Release 603 Until SAPKH60304 |
| Release 604 Until SAPKH60403 |
————————————————————————
|NOT VALID FOR |
|Software Component SAP_BASIS SAP Basis compo…|
| Release 700 SAPKB70001 – SAPKB70008 |
————————————————————————

In transaction SE18 for the enhancement spot MATERIAL_VALUATION_CK, create the following BAdI documentation for the BAdI definition EXTERNAL_OPERATION_VAL_CK:

Use
You can use this BAdI to valuate costing items of the external processing type by entering the info record data (info record number, vendor and purchasing organization) or by setting a price in the method GET_PRICE.
The interface corresponds to the interface of the BAdI SUBCONTRACTING_VAL_CK.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment