Ansicht
Dokumentation

PAY_MX_CFDI_013 - Define different versions of the CFDi statement by town

Fill RESBD Structure from EBP Component Structure   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Using this Customizing activity, you can use different versions of the CFDi statement for different towns.

For example, you define that you want to use version 3.3 for company code MX01, version 3.2 for company code MX02 and version 4.0 for company code MX03.

If you use the same version for all the town, you do not need to run this activity.

To use different versions of the CFDi statement for different towns, you must take four steps in a sequence.

Run this activity and double click on the name of the step that you wish to run:

1. Create an entry for CFDIV with value 2: In this step, you change the CFDIV configuration setting The possible values are the following:

• 0: CFDI 3.3 version activated

• 1: CFDI 3.2 version activated

• 2: CFDI version according to feature .32VER

• 3: CFDI 4.0 version activated

In the standard system, version 4.0 is activated. If you want to use different versions of the CFDi statement for different towns, run this step to create the record for option CFDIV in table V_T5F99K2 with value 2.

1. Create modifiers for CFDIV: In this step, you create modifiers for option CFDIV in view V_T5F99KM, for example:

Opt.	Modif.	Text
CFDIV	01	Version CFDI 3.3 activated for town MX01
CFDIV	02	Version CFDI 3.2 activated for town MX02
CFDIV	03	Version CFDI 4.0 activated for town MX03

1. Enter modifiers in feature 32VER: In this step you change feature 32VER to return the modifier for the configuration setting (that must be on the first line of the feature) and the name of the XML transformation (which has to be on the second line). For further information see the feature documentation 32VER.
2. Create additional entries for CFDIV: In this step you create the additional entries in view V_T5F99K2 for the configuration setting CFDIV, with the modifiers kept in steps 2 and 3, for example:

Opt.	Modif.	Start	End	Value
CFDIV		01/01/1800	12/31/9999	2
CFDIV	01	15/03/2017	12/31/9999	0
CFDIV	02	06/01/2017	12/31/9999	1
CFDIV	03	01/01/2022	12/31/9999	3

In this example there are different versions per town:

• For company code MX01, version 3.3

• For company code MX02, version 3.2

• For company code MX03, version 4.0

12/31/9999

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4407 Date: 20240523 Time: 195441     sap01-206 ( 50 ms )