/scripts/ahub.form.attachments.js
0

Material type not allowed while creating service purchase order

Oct 19, 2016 at 09:38 AM

280

avatar image

Hello All,

User has created new Purchase order document type by copying standard NB. In NB, system is allowing to create service purchase order. But in Z document type, system is throwing error "material type not allowed". As configuration part both NB and Z looks similar. What can be the possible reason for system not allowing in Z but it is allowing in standard.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

6 Answers

Bijay Kumar Barik Oct 20, 2016 at 11:19 AM
1

Did you entered material type for PO creation with NB document type? .......NO

As you are successful in creating service PO with NB document type with item category D, then cross check how Z document type created and did item category D allowed for it

Compare NB document type setting with Z document type for your PO.

Can you share error screen of Z document type with item category D and also share screens of field reference setting detail which is assigned to Z document type in customizing.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hello Bijay,

With NB, we can create service PO with item cat D. NB and Z doc type are same in configuration. We did more testing and found that for Z doc type, we can create material PO only with DIEN material type and not for any other material type. For any other material type like ROH or HALB, system is giving same error "material type is incorrect". It seems there is some code change in the program. At the moment ABAPer is not able to find that. Any idea for such enhancement.

Regards,

Diptanshu

0
Rashid Ali Oct 20, 2016 at 10:35 AM
-1

I think material valuation problem is there , check valuations related field,such as valuation area in the material , material type linking

Share
10 |10000 characters needed characters left characters exceeded
PRASOON AK Oct 19, 2016 at 02:44 PM
0

Hi,

Seems there is some custom validation. Please check the message number and revert back. If its starting with Y or Z, there is an own validation in your system with customer specific enhancement. You may check with your technical team and find the logic behind the validation. There can be some Z tables maintained for document type and any other combination.

Regards,

AKPT

Share
10 |10000 characters needed characters left characters exceeded
Ankur Chauhan Oct 20, 2016 at 06:30 AM
0

Which material type you are using to create service Purchase order.

please revert with as suggest by Prasoon with specific error message!!

because we dont use material type for creating purchase order, all we need to maintain Item category D with AAC.

Please check & revert back!!!

thanks & regards,

Ankur Chauhan

Share
10 |10000 characters needed characters left characters exceeded
Diptanshu Gupta Oct 20, 2016 at 09:22 AM
0

Hello,

There is no message number. But only message type - E, message class - MEPO, object type - BUS2012_HD

We are not entering any material number, just acc. assignement cat as K, item cat as D and service short text. Then in service tab we are entering service number and its detail.

Regards,

Diptanshu

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi,

Seems its customer specific validation. Kindly check with your technical team and find the logic behind the message.

Regards,

AKPT

0
Diptanshu Gupta Oct 20, 2016 at 12:11 PM
0

Hello Bijay,

With NB, we can create service PO with item cat D. NB and Z doc type are same in configuration. We did more testing and found that for Z doc type, we can create material PO only with DIEN material type and not for any other material type. For any other material type like ROH or HALB, system is giving same error "material type is incorrect". It seems there is some code change in the program. At the moment ABAPer is not able to find that. Any idea for such enhancement.

Regards,

Diptanshu

Share
10 |10000 characters needed characters left characters exceeded
Skip to Content