Determination of the COPA movement type in SAP WP2 

COPA postings (KE24 - Extract CO-PA line items)

Movement type: 02 vente externe groupe (external sales to group)

  • If a sale is done to a customer without a trading partner assigned, therefore the COPA document will have trading partner field blank (1) and then the COPA movement type code determined is 02 (2).

Ex: No trading partner is assigned to the customer 2064179 (1) (XD03 - display customer)

=> The movement type 02 is determined when a sale is done to the customer 2064179. 



Movement type: 10 vente inter entrepr. (inter GBU’s sales)

  • When a sale is done to a customer to which a trading partner (1) is assigned, the system needs to assess the consolidation method of the company code assigned to that trading partner code. If with consolidation method fully consolidated (IG) or proportionally consolidated (IP), and there's no additional settings in the related intercompany tables, then the movement type code determined by default will be 10 (2). If with any other consolidation method, the system considers the flow having a movement type 02.


Ex: The trading partner 64270 (2) is assigned to the customer 2095065 (1) (XD03 - display customer)

The consolidation method of the company 6427 is 10 - IG - Fully consolidated (star)



(star)  Determination of the consolidation method of a trading partner in the BFC perimeter SYENSQO

When the BFC perimeter of the company is SYENSQO (=SYEP or SYEW), the consolidation method of the trading partner is done with the Table ZZF_T001_MGT_V - Company codes or with transaction ZWFAT003, running in WP2 only.


When a company Syensqo is not included in the Table ZZF_BFC_CONS_M_V in WP2, it is considered as external even if it is included in the corresponding PF2 tables. 

In other words it means that all companies Syensqo should be included in the Table ZZF_BFC_CONS_M_V  in WP2 (with BFC Perimeter SYEW) even companies managed in PF2 (with BFC Perimeter SYEP)




Then the determination of the partner activity is done using one of the following tables (maintained with ZWFA46A - Financial consolidation/Intercompany): 

Usually the table to be maintained is ZWFAT119 but the full sequence is the detailed here:

  1. Table ZWFAT176 : Company code/IECRA/trading partner/ship-to party  (No longer used)
  2. Table ZWFAT118 : Company code/enterprise/trading partner/PRCOM (No longer used)
  3. Table ZWFAT119 : Company code/enterprise/trading partner
  4. Table ZWFAT113 : FC - enterprises


Ex: The partner GBU is determined in the table ZWFAT119  

When the company code/enterprise (2) /trading partner (1) = ZFR3/ENTR00167/38652 => the target GBU = GY (3)



Movement type: 01 vente intra cdp (intra GBU’s sales)


Whenever there's the need to have a sale with movement type 01 - intra GBU’s sales, the table ZWFAT044 : Company code/trading partner/ enterprise needs to be updated with ZWFA46A - Financial consolidation/Intercompany. 

The request to update the table ZWFAT044 is done through Service One. The requester needs to provide the issuing company, the buying company and the related ENTRP/BU code.

Ex: The sale from company ZFR3 to trading partner 64200 (1) is an intra GBU sales when it is done through ENTRP00222 (2). The movement type = 01 - intra GBU's sales

The determination of the movement type = 01 is done with the table ZWFAT044

When the issuing company = ZFR3, the buying company = 6420 (TP 64200), the enterprise code = ENTRP00222 (2) => the movement type = 01 (1)

Tables ZWFAT041, ZWFAT042 and ZWFAT043 are not updated anymore as there are too specific. Nevertheless, the COPA movement type determination process reads all the tables in sequence until it gets the entry with the required data, if an entry is not set, the generic rules apply.



Other movement types


It is no longer common to update the tables with other COPA movement types available in SAP WP1.