Inbound Processing : Error when changing a BOM

[former_member611006]

Hi Experts,

I have the following error when I send a BOMMAT IDoc in "Change" Mode (Editing the BOM, to recreate the History inthe Target system) :

Start processing in API: CSAP_MAT_BOM_MAINTAIN
Group BOM
Changes to the BOM exist after 03.11.2008
Date 03.11.2008 copied from change number
Item (1) 0040 L 000000001084237016 000000000000000000000000  cannot be uniquely identified
Item (3) 0100 L 000000001084237021 000000000000000000000000  cannot be uniquely identified
Item (6) 0200 L 000000000768041196 000000000000000000000000  cannot be uniquely identified
End of processing in API: CSAP_MAT_BOM_MAINTAIN

Any idea ?

Regards,

David

[former_member611006]

Hi Experts,

now I have another problem :

When I maintain a BOM via ALE, I have the following error in the Target system :

"Long text does not exist" with Status 51.

I've tried to search some SapNotes for CSAP_MAT_BOM_MAINTAIN and IDOC_INPUT_BOMMAT but they are all present in the system.

Any idea ?

Regards,

David

[Former Member]

HI David,

you can debug this.

Go to Your FM (found through your Processcode inbound).

Set your breakpoint at first statement and walk through.

maybe try to use watchpoint for idoc-status field.

[former_member611006]

Hi Gordon,

the problem is that "Item Text" are not saved in the Target System ( IDoc contains all Item Text with Include but it's not saved by the Inbound Process)

All SapNotes are present in the Target System.

Any Idea ?

Regards,

David

[Former Member]

David,

do you have checked the spro customizing ? Maybe there is an option to enable this !

[former_member611006]

Hi Gordon,

I think I found something.

When I create a BOM with ALE in the Target, no problem. Then when I want to update it, I've got this error ...

In the Source, we're working with Text Object for Text Item (INCLUDE Text ID). But in the Target, Text Object doesn't exist, and when we update or modify the BOM via ALE, the Inbound Process try to find the old Text Object before updating it with the new one ...

I think the solution is to create all Text Object/ID (Ta SO10) in the Target ... I don't understand why the ALE Inbound Process doesn't create Text Objects if they don't exist...

Regards,

David

[Former Member]

Hi Mark,

I was curious what the solution was to the 'Could not uniqueliy be identified' error.

Regards,

Bubble

Edited by: Bubble on Jun 22, 2010 10:48 AM