Packing Requirements Data importing issues for UN_LIS_SUB Spec using OCC approach

[Ramu-Mannava]

Hi experts,

Property Tree = LS_UN_TREE

TAB = Packing Requirements

I am doing UN_LIST_SUB spec import using OCC(for Packing requirements Data only)

As per the SAP Standards, we cant import the Packing requirements TAB data using standard CG33 Specification Import. (I have experienced this practically too)

So i tried to achieve this by using the OCC.

When i am trying to import this data using the OCC i am facing the below issues

1. There is a field called Instruction for Enclosure in the Packing requirements Tab in LS_UN_TREE.
2. The data for the particular field Instruction for Enclosure is not able to import using OCC. I am not sure why this is happening where as its importing all other fields beside that field.
3. As per the Log file the issue is, "Found INSTR_ENCL not expected. Invalid Data Element".
4. The filed beside that is Risk Potential. And the Technical Name for this is DPOT. System is not showing any errors/issues with the other field like this.
   But the problem is with the INSTR_ENCL: Instruction for enclosure
5. As i can see that this field INSTR_ENCL is coming from the table CCUNTPACK and the field is present in the check table CCUNC115.
6. But as per the OCC excel format we maintain doesn't contain any table information but the field information only.Like below,

• Risk Potential = K:DPOT
• Instruction for enclosure = K:INSTR_ENCL

So, i am not able to import the data for this instruction for enclosure filed this is where system is generating error in the log file as mentioned in in the point 3.

Your suggestions will help me a lot, Kindly suggest,

Thank you so much.

Best regrds

Chowdary

[satya11719]

Hello mannava.ramu

Please use OCC online mode , it will get updated.

Thanks

Satya

[Ramu-Mannava]

Hi Sathya,

Thanks for your reply,

We have done it online mode too. And the data is imported for all other fields except the data for the field instruction for enclosure. This field is filling blank/no data.

kindly suggest, this will help me a lot.

Thank you so much,

Best regards

Chowdary

[christoph_bergemann]

Dear Chowdary

what specification type does specification "UNSPEC" have ? (and why do you use "named" specification ids..? Many companies just use "Numbers" (like 12345)

As mentioned: I propose to use "debug"; the "warning" statement in the log is coming from some place in "ABAP". Here you should try to "stop" the process

I assume you have fully customized your system; so the value "E0" in your load file is valid (existing in customizing table)

C.B.

[neha_reddy2]

Hi Chowdary,

Your OCC template file seems to be fine as the entries are matching with table CCUNTPACK. But, the data in your file for the field Specification Category is maintained as LIST_SUB infact it should be LS_UN_SUB .

Could you try to upload by changing it ?

Regards,

Prasad Gudikandula.

[christoph_bergemann]

Hello

referring to

"

1. But as per the OCC excel format we maintain doesn't contain any table information but the field information only.Like below,

• Risk Potential = K:DPOT
• Instruction for enclosure = K:INSTR_ENCL"

I still have now clue regarding the contetn of your EXCEL file

But what is clear (from my point of view): this data has a "refernce" to "DPOT" (so what ever data you would liek to load: you must specify the "DPOT" etc.

So I stll believe that the content of your EXCEL file is not correct and therefore y<ou can not load

C.B.

PS: may be check: https://help.sap.com/doc/erp_hcm_ias_2013_01/1.0.3/en-US/46/40196481bd08e7e10000000a114a6b/content.h...

https://help.sap.com/saphelp_globext607_10/helpdata/en/46/48c2220f5e0dbae10000000a1553f6/frameset.ht...

here you will find some explanation why you need (may be) this kind of data

PPS: check https://help.sap.com/doc/71bd5965faad411aa1f1242b4370f61e/EHP08/en-US/OCC_Specification_and_Phrase_I...

page 17; hereyou will find sometthing; please check chapter 6.2.5 of the document; may be this helps

[satya11719]

Hello mannava.ramu

Instruction for enclosure = K:INSTR_ENCL, your OCC contain this field ? I'm not sure how you are handling this data in OCC template.

There are some clues below,

I could see text table is CCUNC116

CCUNC116 is a standard SAP Table which is used to store Descriptions for Instructions for Enclosure data and is available within R/3 SAP systems depending on the version and release level.

Delivery Class: C - Customizing table, Maintenance only by customer and not updated by SAP import.

Hope it helps.

Thanks

Satya

[Ramu-Mannava]

Hello Satya,

Thanks for the reply ,

Yes, I have this field in the OCC file as shown in below, please suggest

[christoph_bergemann]

Hello

this sentence is not clear to me:

"I am doing UN_LIST_SUB spec import using OCC(for Packing requirements Data only)"

Something like "only" is not really possible (or misinterpret you).

Example: if you would like to create "density" data some "minimum" data is needed in the "EXEL file". In theory you can may be generate one data record containing only ! Usage" but this does not really make sense (from data perspective: we have to "different" the user point of view and the technical point of view; but this is a different story)

Can you show one CG02 dialog with some data (so that we can be sure what you would like to load

PLease show the data in the "EXCEL" file

Regarding "As per the Log file the issue is, "Found INSTR_ENCL not expected. Invalid Data Element"."

If you have load data for one spec only now you can look for the help of an "ABAPer".

The message (refer above) is linked to some "message class" in SAP with a "number". This "message" is created somethere in ABAP code: You can try to prepare a "break Point" and start there any analyse: what is happening

Can you please show (for safety reasons) your customizing set up? SPRO is only saying something like this: if you use this "example function" module you can start the load with OCC.

C.B.

[Ramu-Mannava]

Hello C.B,

Thanks for the reply ,

For your information, Please see the file format that i am using to import "Packing requirements Tab" data for UN_LIS_SUB.

KIndly suggest