BC4.8 Problems with IDOC Lookup (ORDERS05 agains 4.7)

[S0001010997]

Hi all,

we are experiencing problems trying to send an flat IDOC to a 4.7 Enterprise backend system. We try to build up a valid IDOC out of an flat file using service pub.sap.idoc.decodeString. This service delivers not the correct hierarchy of the IDOC back.

Serivce sap.admin.idoc.getIDocDefinition delivers only the following result:

E1EDK01 E2EDK01005 1 true 1 false IDOC: Belegkopf Daten allgemein

E1EDK14 E2EDK14 2 false 12 true IDOC: Belegkopf Organisationsdaten

E1EDK03 E2EDK03 2 false 10 true IDOC: Belegkopf Datumssegment

E1EDK04 E2EDK04001 2 false 10 true IDOC: Belegkopf Steuern

E1EDK05 E2EDK05001 2 false 16 true IDOC: Belegkopf Konditionen

E1EDKA1 E2EDKA1003 2 false 99 true IDOC: Belegkopf Partnerinformationen

E1EDK02 E2EDK02 2 false 10 true IDOC: Belegkopf Referenzdaten

E1EDK17 E2EDK17 2 false 4 true IDOC: Belegkopf Lieferbedingungen

E1EDK18 E2EDK18 2 false 3 true IDOC: Belegkopf Zahlungsbedingungen

E1EDK35 E2EDK35000 2 false 99999 true IDOC: Belegkopf Zusatzdaten

E1EDK36 E2EDK36000 2 false 99 false IDOC: Belegkopf Zahlungskarten

E1EDKT1 E2EDKT1002 2 false 99 true IDOC: Belegkopf Textidentifikation

E1EDP01 E2EDP01006 2 false 999999 false IDOC: Belegposition Daten allgemein

E1CUCFG E2CUCFG003 2 false 99999 false CU: Konfigurationsdaten

E1EDL37 E2EDL37004 2 false 999999 false Handling Unit Kopf

E1EDS01 E2EDS01 2 false 5 true IDOC: Summensegment allgemein

which is not the total IDOC structure of ORDERS05 (seems to be only level 1 and 2. Levels 3 and bigger are missing).

Any ideas? Problem with the java version? BC bug?

BR

Richard

PS: BC-user on the backend has SAPALL/SAPNEW rights

[Former Member · Accepted solution]

Hi,

did you import the IDoc definition directly from the connected SAP system to your SAP BC Developer tool? Doing this should provide the correct IDoc structure which your should be able to include in your flows.

Choose SAP -> IDoc Definition from the menu.

2 Select an SAP Server and enter the IDoc type you are looking for. click on Lookup.

3 The IDoc structure is displayed now. If you want to generate a record from it, click on

Generate record.

Regards,

Kai

Edited by: Kai Lerch-Baier on Aug 13, 2009 10:42 AM

[S0001010997 · Accepted solution]

Hi,

no. The used service decodeString imports an IDOC in flat-file format and makes a lookup in the provided SAP system for structural information. This works correctly this way in BC4.6 release. Any further ideas?

BR,

Richard

[Former Member · Accepted solution]

Ok, so this may be an issue of either JAVA version or Java IDoc Class Library.

See this migration guides for upgrades from 4.6 to 4.8 here:

https://websmp207.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000047738

A migration guide that describes the general considerations necessary when upgrading from 4.6/4.7 to 4.8. It also describes how to use the Transfer package. SAP BC 4.6/4.7 to 4.8 Migration Guide as pdf file (907 KB), June 8, 2009

A package that can be installed on all BC 4.x versions and enables an easy transfer of configuration and customizing settings from one BC to the other. SAP BC 4.6/4.7 to 4.8 Transfer Package as zip file (13 KB), June 8, 2009

A special guide describing the steps that are necessary, if you wrote IDoc mappings for SAP BC 4.7 using the Java IDoc Library 1.0. SAP BC 4.8 now uses the Java IDoc Library 3.0, which requires slight adjustments to your Java code. IDoc Library Migration Guide as pdf file (172 KB), July 02, 2008

[S0001010997 · Accepted solution]

Hi,

yes could be a Java problem. But i do not use any java code in my services, only standard BC and SAP services. So I hoped, that anything will work exacly the same on 4.8

I'll check the migration guides again. If anybody has more infos, please post.

BR,

Richard

[Former Member · Accepted solution]

Richard,

an additional hint: you may also post your question to http://wmusers.com/forum/. Maybe someone there already faced same problem.

Regards,

Kai

[former_member745782 · Accepted solution]

hello,

i have the same problem whit the same Idoc (and BC48).

Somebody solved this problem?

[former_member745782 · Accepted solution]

customer decide to change integration software (non SAP) :(((

anyway thanks

Edited by: apederiva on Oct 5, 2009 10:08 AM