22

_______________________________________________________________________________1

PI INTERFACE 7.0 - FI

If you already have done the SD PI Interface configuration, please just follow steps:2. Import IDocs (FIDCC02 )3. Import Interface (from TPZ file)10. Create Receiver Determination11. Create Interface Determination

Step by step solution:

1. Import Software Component Versions from SLD2. Import IDoc ( FIDCC02 )3. Import Repository configuration (from Tpz file)4. Create Data Types (already done in Step 3)5. Create Message Type (already done in Step 3)6. Create Message Interface (already done in Step 3)7. Import Java Mapping (already done in Step 3)8. Create Interface Mapping (already done in Step 3)9. Assign Business System10. Create Communication Channel11. Create Receiver Determination12. Create Interface Determination13. Create Receiver Agreement

1. Import Software Component Versions

Start XI and type/access SXMB_IFR to launch your integration builder, or type"http://<server>:<port>/rep in your browser's address bar, then hit enter.

This will launch Integration Builder.

1.1. Click on Integration Repository and import all your definition from SLD (system landscapedirectory) from the TOOLS Transfer from System Landscape Directory menu option.

_______________________________________________________________________________2

1.2. When you do this, the system will prompt you with all the available SWCVs from SLD andhave the chosen one imported into the Integration Repository

So, we have our SWC and corresponding version available for us to begin with. Double-clickon SWCV then bring it to the edit mode. Enter the required info after switching to the"IMPORT RFC/IDOC............" radio button displayed in the work area. This is essential, asthis will then be used for importing IDocs from the source system.Make sure the IDoc has already the extension definition (OSS Note 1321680).

1.3. Click on the "+ " icon at the bottom part of work area appearing just below the server info.This will give you the option to enter the NAME SPACE. Enter"http://www.sat.gob.mx/cfd/2".

_______________________________________________________________________________3

1.4. Save the work, and then activate it.2. Import IDoc (FIDCC2.FIDCCP02.ZDM_FI1*):*In this guide, the IDoc extension’s name is ZDM_FI1. You shall replace this name with the one you defined in yoursystem.

2.1. Right-click on Imported Objects and Import of SAP Objects.

2.2. Enter the Application Server and the System Number from your R/3 System.

_______________________________________________________________________________4

2.3. Select the object FIDCC2.FIDCCP02.ZDM_FI1

2.4.Click on Finish to Import:

3. Import Interface (from TPZ file):

In the Integration Repository , click on Tools >> Import Design Objects.

_______________________________________________________________________________5

Select import Source “Client” for looking your file tpz in your PC.

Save and activate all objects.File: XI3_0_FACTURA_ELECTRONICA_0.1_of_sap.com.mx.tpz

4. Create Data Types (already done in step 3):

Create the Data Type and build the structure into which the data from R/3 IDoc shall bereceived. After expanding the NAME SPACE, expand the INTERFACE OBJECTS. Then rightclick on DATA TYPES to start creating.

For this purpose we define followings Data types

_______________________________________________________________________________6

4.1.Data type: Comprobante

4.2. Data type: C_Emisor

4.3. Data type: t_UbicacionFiscal

_______________________________________________________________________________7

4.4.Data type: t_Ubicacion

4.5.Data type: C_Receptor

4.6.Data type: C_Conceptos

_______________________________________________________________________________8

4.7.Data type: t_importe

4.8.Data type: t_InformacionAduanera

4.9. Data type: I_CuentaPredial

_______________________________________________________________________________9

4.10. Data type: C_Impuestos

4.11. Data type: C_Addenda

You can see in the Law: “Anexo_20” the complete format about target structure (XML Structure).

5. Create Message Type (already done in step 3):

_______________________________________________________________________________10

5.1.Message Type: Comprobante_MT

6. Create Message Interface (already done in step 3) :

6.1 To do this, right-click on the MESSAGE INTERFACE title and create the new object. Herewe will make sure that the attributes are set to ASYNCHRONOUS (will see this later) andINBOUND (into XI from R/3).

6.2 Drag and drop the INVOIC.INVOIC02 from Imported Objects IDOC on to the hand icon onthe right-hand side next to name space field. Or drop down the list then select the messagetype from the resulting window. Or simply type the details.

Message Interfaces: MT Comprobante

_______________________________________________________________________________11

At this stage we are done with definitions and now its time to map the messages and interfacecreated thus far.

7. Import Java Mapping (already done in Step 3):

At this step you need to have a Java Class who is going to do the Mapping between IDOCINVOIC02 and the target message MT_Comprobante created as stated above.

7.1 To begin with, click on the triangle pointing rightwards on MAPPING OBJECTS. Right-clickon Imported Archives and create a new.

7.2 Put a Name to import

_______________________________________________________________________________12

7.3 Use Import Button to import the Zip file that contains the Java Class

Java Mapping is needed to map the SOURCE to the TARGET. In our case the source is the R/3IDoc coming into XI from SAP R/3 and the target is a XML FILE stored at root directory that willthen be accessed by any script to load in to the destination system.

In Java Class we are creating a 1-1 kind of relationship between the source and target.

8. Create Interface Mapping

Now, the last step in the Integration Repository is to create the INTERFACE MAPPING. In thisstep map the source (FIDCC02.FIDCCP02.ZMD_FI1) to the target interface (MI_Comprobante).

Once the objects are identified and filled into respective fields, click on the “Read Interfaces”push button on the right-hand side in the bottom portion of the work area. This replicates thesource and targets into the Request Tab Window.

Identify the message mapping program created in the above step and assign it here.

Interface Mapping: OM_CFD_FI

_______________________________________________________________________________13

We are done with SOURCE, TARGET, and LINK for data handling.

Save the work. This is time to check the object consistency. Make sure to hit “F7” at thisstage just before activating. At the end activate the change list.

9. Assign Business System:

Create a new Scenario.

_______________________________________________________________________________14

Click on Integration Directory

Service without Party Business System, right-click on Business System and AssignBusiness System.

Select the business system to define as the business system service.

_______________________________________________________________________________15

10 – Create Communication Channel

To create communication channel, right-click on Communication Channel and New.

And create de object where CC represent (Communication Channel)

_______________________________________________________________________________16

Choose Adapter Type: File; Receiver and the Target directory on the server for XML’s

_______________________________________________________________________________17

11 – Create Receiver DeterminationTo create, right-click on Receiver Determination and New.

Create this Object using Interface FIDCC02.FIDCCP02.ZMD_FI1

_______________________________________________________________________________18

_______________________________________________________________________________19

And select the Communication Component.

12 – Create Interface DeterminationTo create, right-click on Interface Determination and New.

Now create the Interface Determination.

_______________________________________________________________________________20

Select the Message interface and the Interface Mapping

_______________________________________________________________________________21

13 – Create Receiver AgreementTo create, right-click on Receiver Agreement and New.

Create the Receiver Agreement using Message Interface MI_Comprobante.

_______________________________________________________________________________22

Select the communication channel that has been created before.