Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Issue using UOM 'AU' with BAPI_CHARACT_CREATE

Former Member
0 Likes
1,205

I'm attempting to use BAPI_CHARACT_CREATE to create characteristics and I'm encountering an issue when I try to use the 'AU' unit of measure (activity unit). When I provide AU to the bapi, I don't get an error, but the uom on the characteristic is blank. If I use other uom's (EA, etc), the characteristic properly displays the uom.

When entering characteristics via the front end (tcode: CT04), I'm able to use AU and the characteristic saves and stores the value correctly.

Is there something "special" about the AU unit of measure that prevents its' use with BAPI's? I've noticed that AU is not configured in the CUNI tcode like the others, but it obviously exists somewhere since it's available via the uom drop down lists.

Any and all suggestions are welcome.

Thanx in advance.

er

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
884

Issue Resolved.

The 'AU' unit of measure was failing validation when the characteristic was being created. The BAPI checks again table T006A with a table key of LANGUAGE and UOM. The AU value is a translated value for the EN language and the actual key value in the table is 'LE'. Once I use the LE value in my load, the AU unit of measure was properly applied.

1 REPLY 1
Read only

Former Member
0 Likes
885

Issue Resolved.

The 'AU' unit of measure was failing validation when the characteristic was being created. The BAPI checks again table T006A with a table key of LANGUAGE and UOM. The AU value is a translated value for the EN language and the actual key value in the table is 'LE'. Once I use the LE value in my load, the AU unit of measure was properly applied.