BOMMAT inbound Idoc error

[Former Member]

Hi Experts,

I am trying to process an inbound BOMMAT Idoc from external system to SAP in WE19 and getting the error that internal unit of measure has no language dependent settings. I tried with 2 materials with unit of measure PC and also EA but same error . It seems some settings related to CUNI or MM02 are missing. The dump says 'In perform or CALL FUNCTION "CONVERT MATNR TO INTERN_FORMAT", the actual parameter "MATERIAL' is incompatible with the formal parameter "I_MATNR". I made some entries in CUNI for PC, but error exists. Can you kindly help please.

Thanks

Sakthi

[JL23 · Accepted solution]

What you described does not sound logical to me or you are mixing 2 error situations in this single question.

regarding the unit go into your customizing (transaction CUNI) and you will see the internal unit and also the commercial and technical unit with their descriptions.

An internal unit can be quite different from the commercial unit, an on top of this the commercial unit and technical unit is even translation relevant.

Technically you can see in T006 table and T006A table (hint: do not enter any selection in SE16 for these tables, always execute to see all hits, then use the search or filter option in the result)

Then you are talking about a dump without showing the dump, you also mention a function module that does not exist in this notation.

the mentioned inconsistency of parameters usually means that the function module expects e.g. 3 parameters and you only provided 2, or you entered characters into a numeric field.

[Former Member · Accepted solution]

Hi Jurgen

I created a BOM in SAP and sent it to external system via BD30 and the outbound idoc processed successfully. Now I want to manually trigger the same BOMMAT idoc in WE19 as inbound idoc from external system by interchanging the sender and receiver. Now it creates the short dump. for some Material BOM transfers, it shows the language dependent settings are not defined for the internal unit of measure. When searched the forums I thought it should be related to CUNI.

Thanks

Sakthi

[JL23 · Accepted solution]

I would not expect to get a valid inbound Idoc by just exchanging sender and receiver of an outbound idoc. Even it is a copy of your own Idoc and you might think that the units are known to your system, practically it is  different.

if a person is speaking Japanese and you speak French then you just can't talk to each other as you do not understand what the other is saying. You either need a translator or if the capabilities are there you can both talk in English.

Nothing else does the Idoc. The units in the Idoc should usually be maintained by the value of the Iso code. The idea behind the Iso-codes was to have a global norm for the same unit.

If one says パック then it has to be translated to ISO code PK  in the Idoc

you receive the IDoc and the import program is using the PK and browsing table T006 to find the unit which is assigned to PK as primary unit, so it should find PAC in your system.

Starting with this general logic it can be assumed that the system uses the value that you have in the unit fields and considers it as Iso code, finds then a unit based on above logic  which is not translated. Or it does not find an corresponding ISO code at all and dumps for that reason. (Info records also dump if the unit is not an Iso Code)

[Former Member · Accepted solution]

Thanks Jorgen. The unit I see in the Idoc segments is PCE -Piece. Can you please suggest a solution how I could process the inbound Idoc successfully and what are necessary things need to be set for the language related error to disappear.

Thanks

Sakthi

[JL23 · Accepted solution]

PCE is in general ok as this is the ISO unit, still you have not said which unit it finds from T006 table as several units can have PCE as Iso unit, but only one can have the primary indicator, and this is the one that is used for posting and has to included in your material master as alternative unit.

My preferred way of investigating an Idoc is ALE and LSMW. I send the idoc by ALE to a file, then prepare an LSMW to read that file and to create again an IDoc of the same kind. Finally I can see the new IDoc in the usual transactions like WE02 BD87 etc.

I described this way in my blog

Is of course a longer way, but gives me a lot confidence. You could also check the control data of other inbound Idocs via BD87, eventually helps this also a step further.

[Former Member · Accepted solution]

Hi Jurgen

ISO Code -PCE has in T006 table, the Int.meas.unit (Unit of measurement) as ST, Commercial unit- PC & Technical unit -PC. Where does it pick ST from and should it be changed ? where should I add ST in MM03. Now I have only PC as Base unit of measure in MM03.

Thanks

Sakthi

[JL23 · Accepted solution]

SAP uses the internal unit of measure everywhere, you just do not see that because of a conversion exit which converts the internal unit into the commercial unit in your logon language.

ST is German and the abbreviation for Stück, which is piece in English.

If you want to see the internal unit then use SE16, select in the menu the user settings and remove the X from the box for "use conversion exits"

[Former Member · Accepted solution]

Hi Jurgen,

SAP note 1940837 is needed for this error fix. Thanks for your guidance,

Thanks

Sakthi