Inbound BOMMAT idocs failing with MSG BOM 023

Advertisement
November 30

We're taking in BOMMAT idocs into an ECC6.0 system from an external system and I have some failed idocs with message BOM 023 - local BOM <material> <plant> <alternative> cannot be changed via ALE.
We're doing create and change functions  - this one is a change with MSGFN = 005
There are no multiple BOMS, alternative 1 the only 1.
I haven't been able to find any sensible explanation for this message and I haven't seen it before . Can anyone throw any light on it?
Thanks,
Jonathan

Advertisement

Replay

Hi Jonathan,
You are trying to change a BOM on SAP that was not initially transfered-created via the interface. Instead it was firstly created manually on SAP. For this reason you get the message for local BOM that cannot be changed via ALE. You can also confirm this also by the ALE indicator on BOM header (field STKO-ALEKZ for the given BOM).
Br,
Petros

View 2 Replies

Tags:

  1. 3 G net worksettings of apple l phone
  2. migo stock type
  3. breakpoint reached on Lenovo G 50
  4. application nokia rm-243 6120c(b20.01)
  5. sattellite l650 1mm system unit psk1 je
  6. pubsubagent making cpu run at 100
  7. claiming primary bt id status
  8. does STATUS_CHANGE_EXTERN COMMIT WORK
  9. 3D8Y
  10. 1DC5
Copyrights 2019 Fcffair BigData Resource, All rights reserved