Configuracion Idocs PI 7.

31

http://help.sap.com/saphelp_nw73/helpdata/en/c2/91865252c84716b3b8be394851c9c0/fra meset.htm

Configuring the IDoc Adapter (Advanced Adapter Engine)

You use this procedure to configure an IDoc adapter (AAE) that transfers information between SAP or non-SAP systems using IDocs (intermediate documents).

Prerequisites
You have created an RFC destination with a name XI_IDOC_DEFAULT_DESTINATION, and you have configured it on the adapter engine using the NWA

RECOMMENDATION The destination must point to an SAP application system that contains metadata for frequently used IDoc types as the RFC destination. More information: Maintaining RFC Destinations

You have configured the inboundRA resource adapter and set the following properties using the NWA: o MaxReaderThreadCount has a value between 5 and 10 (both inclusive).

o o

GatewayServer: The Gateway server that you use for inbound communication in default mode. SAP recommens you to use the gateway server of central PI system. GatewayService: The Gateway service that you use for inbound communication in default mode. SAP recommends you to use the gateway service of central PI system. The gateway service should be the service of the gateway used in the property GatewayServer. You must ensure that the sender system sending messages to idoc adapter via a sender channel configured in Default mode uses the same GatewayServer and GatewayService.

You have configured the JavaIdocAdapter resource adapter and set the following properties using the NWA or using the link http://<hostname>:<port>/nwa Configuration Infrastructure Application Resources , In the Show, select Resource Adapters, in the Resource List table, select JavaIdocAdapter and in the Resource Details table, select Properties. o Persistance If you want the IDoc information to be persisted in the DB, set the value to true, else set the value to false.

NOTE By setting the value to false, monitoring and acknowledgments cannot be monitored. When the value is set to false there is no database operation and hence the IDocs are processed faster. AutoNumberFromDB If you want sequential IDoc numbering for the receiver IDoc adapter set the value to true, else set the value to false.

NOTE In some cases (DB isolation and locking levels) setting the value to true can result in IDoc number clash, in such cases change the value to false. When the value is set to false there is no extra database operation and hence the IDocs are processed faster.

NOTE You can leave all the other properties unchanged. More information: Configuring Resource Adapters and JCA Connection Factories in NW

Procedure
1. Configure the sender IDoc adapter (AAE) and the receiver IDoc adapter (AAE) in the Integration Builder. More information: Configuring IDoc Adapter (AAE) in the Integration Builder 2. Configure the sender system to process IDocs. More information: Configuring the Sender System to Process IDocs 3. Configure the receiver system to process IDocs. More information: Configuring the Receiver System to Process IDocs

NOTE You must activate the configuration scenario and all the entities that are added to it using the activate option in the Integration Builder.

More Information
The characteristics of the IDoc adater (AAE) are discussed in a different topic. More information: Characteristics of the IDoc Adapter (AAE)

IMPORTANTE-> Una vez transportado, editar y activar los canales Idoc. Para evitar el siguiente error:

El connection Factory no lo estamos usando, asi que no tiene mucho sentido el error, hay que editar el canal y modificar el nombre del destino y luego corregirlo:

Error nuevo (Metadata not available)

Note 1406965 - Java Idoc Adapter/Module Authorizations

Summary Symptom For Java Idoc Module and Java Idoc Adapter you get error Message processing failed. Cause: com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: The metadata for the parsed IDoc was not

available. See cause exception for details. : state=READING_ENDTAG, charPosition=0, lineNumber=0, columnNumber=0 Other terms Java Idoc Adapter, Idoc_AAE Reason and Prerequisites Authorizations for user is not available to access Idoc repository Solution Pls ensure that fllowing Notes are applied. 1. Note 460089 - RFC Authroizations 2. Note 974537 - Idoc authorizations. Also : Make sure that the user has sufficient authorizations. You need the S_IDOCDEFT (EDI_TCD = "WE30"; ACTVT = "03") authorization. If this donot solve the problem : 1) Pls provide new traces (as per Note 1359226) 2) Attach entries in table TACTZ for the Object S_IDOCDEFT.

SOLUCION El Idoc no existe en DK0, por eso no puede leer los metadatos!!!