Co$ta - Package assignment

>> Back to the  Co$ta project  home page



Main Principles

The determination of the subpackage is done in 3 steps :

  1. There is a material code in the posting, then the program assigns the posting using its material group 
  2. When there is no material code, then the program uses the material group of the purchase order when there is one to determine the subpackage
  3. Where there is nor material code, neither purchase order, the determination of the subpackage is done using the cost element of the posting.




Exceptions 

  • Samples in PF1: Postings are done directly in COPA (Origin flow: COPA) in the value field VV151 which is fully assigned to the sub-package P20027. 
  • IFRS16 Lease (Origin flow: WCFI_LEASE): When there is neither article nor purchase order, the determination of the subpackage is done with the segment of vendor (mainly for cars and BGRS costs). 


Package Derivation Source

The dimension "Package Derivation Source" is used to see how the sub-package is assigned to a posting: 

  • MATERIAL: There is a material code in the posting. A material group is assigned in its master data that is itself assigned to a sub-package,

  • PURCHDOC: There is no material but a purchase order. There is a material group in the purchase order that is assigned to a sub-package,
  • COSTELMNT: There is neither material nor purchase order. The cost element is used to assign the sub-package,

The Table ZTFI_CESBPKG - Cost elements Subpackages mapping is used to map the lowest level cost element group from the ZSOLV hierarchy to the cost sub-packages. 

  • VFIELD: This dimension is only used when the origin flow is COPA. Some postings are done directly in COPA and in some cases the assignement to a subpackage is done based on the value field used for the posting, 
    • For instance Samples in PF1 are posted in the value field VV151 which is assigned to the subpackage P20233. 
  • VENDOR: This dimension is only used when the origin flow is WCFI_LEASE. When there is neither article nor purchase order, the determination of the subpackage is done with the vendor. 
  • NERPSYST: This dimension is only used when the origin flow is NERP. The subpackage is maintained in the file TEMPLATE ZCBS_BW that is loaded manually in BW.



Unassigned packages

In some cases a package can not be assigned. 

When the assignement is not possible, there is a reason code in the column Cost Sub Package.



  • NC_MATNR (1): There is a material code with a material group but the material group is not assigned to a sub-package. 

In the example, the material group 0112 (2) is assigned to the material code 1062492 (3) however the material group 0112 is not assigned to a sub-package in the transcodification table. 

=> The material group 0112 should be included in the table and assigned to a sub-package. 




  • NC_PURDOC (1): There is a purchase order with a material group but the material group is not assigned to a sub-package. 

In the example, the material group 0078 (2) is not assigned to a sub-package in the transcodification table. 

=> The material group 0078 should be included in the table and assigned to a sub-package. 



  • NC_FIN (1): There is a cost element that is not assigned to a sub-package. 

In the example, the material group 98120010 (2) is not assigned to a sub-package in the transcodification table. 

=> The material group 98120010 should be included in the table and assigned to a sub-package.