cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Issue with generic packaging specification for VAS process

Former Member
0 Kudos
2,050

Hi All,

We have a requirement where, we need to have a generic pack spec with 2 packing levels. And this generic pack spec should be used for Internal VAS order creation for any of the product.

So, I have created a pack spec without product mentioned in the content then maintained the condition record accordingly. When I tried to create an internal VAS order using this pack spec then getting below error,

Note: Here I had entered the pack spec number manually. Even if i dont enter manually, system determines the same pack spec based on condition record. But in the end when i click on OK, getting below error. So VAS order not getting created with generic pack spec.

Could you please let me know, what is the settings that I am missing here.. Please help me with your suggestion.

Regards,

Laxman

Accepted Solutions (0)

Answers (4)

Answers (4)

Ajit_Routray
Active Contributor
0 Kudos

Hi Laxman,

Could you please try the below procedure for Pack Spec ( Reference Product Main. ) and let us know if it fulfill your requirement.

Steps:

1> Maintain Pack spec for Product-A with content as product A .

2> Also maintain condition record for auto pack spec determination

3> Maintain Ref.P for Pack as Product-A ( Tcode-/SCWM/MAT1 - Maintain Warehouse Product->Pkg Data Tab-> Ref.P for Pack ) in Product B....Others.Maintain condition record of product B for auto pack spec determination..

4> Create VAS order for Product B. Please check without/with packspec .

Kind Regards,

Ajit

Former Member
0 Kudos

Dear Ajit,

I have tried as you had suggested and it worked well. Now the pack spec of Product ' A', is getting determined for Product 'B' while creating VAS based on condition record.

Thanks for your help.

Regards,

Laxman

Former Member
0 Kudos

Hi Ajit,

Though the suggested solution working fine, this require lots of data maintenance as for all the products we should maintain the reference packaging material for pack (Ref.P for Pack) and in condition record of packaging specification we should maintain all the products.

But customer requirement is to have this scenario work fine without lots of data maintenance. So this require custom development.

Regards

Laxman

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

"If so then why its not working in case of VAS?"

It simply doesn't work.

"Also I had used the same packaging specification for auto packing at ID creation by maintaining the condition record 0IBD. HU is getting created without any error though product is not mentioned in the pack spec."

Just tried - did not work for me. And I would have been surprised if it would have.

Brgds

Juergen

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hm, must correct myself. I tried, but with the condition record 0PAL (that is what I usually use to show), and with that it did not work. With 0IBD indeed it did work - which does not really make any sense for me now.

Former Member
0 Kudos

Dear Juergen,

Yes, when I add the product in the content of packaging specification and tried to create a VAS. Its working fine without any issue. But when I try without product then its giving an error as I mentioned earlier.

Also I had used the same packaging specification for auto packing at ID creation by maintaining the condition record 0IBD. HU is getting created without any error though product is not mentioned in the pack spec. If so then why its not working in case of VAS?

How can we achieve this requirement?. Because as per client requirement, there should be a one pack spec which can be used in VAS for any of the product.

Regards,

Laxman

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

have you tried with a packaging specification which includes a product? Eventually it is simply not possible to use a generic packaging specification here.

Brgds

Juergen

---
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/curriculum/scm_ewm
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

And it is EWM. NOT eWM - Duh!