- SAP Managed Tags:
1. Item category for purchase requisition(EBAN - PSTYP):
There are a lot of item categories defined for purchase document, but only some of them are supported to transfer to SRM system.
This is hard-coded in LBBPKF01/FORM GENERAL_CHECKS:
Only the following categories are supported:
For Subcontracting items, Government Procurement flag should be checked. You may refer to the following link for subcontracting infomation:
http://help.sap.com/saphelp_srm70/helpdata/EN/91/c9fa2d0ddc42ea9b7d2117acdefcf5/frameset.htm
2. If report BBP_EXTREQ_TRANSFER is used to transfer PR, both tables V_T160EX and V_T160PR should be maintained well.
- For table V_T160EX, material group(MATKL), purchasing group(EKGRP) and profile(EPROFILE) can be maintained.
Customizing path:
SPRO->..
SAP Customizing Implementation Guide
Integration with Other mySAP.com Components
Supplier Relationship Management
Plan-Driven Procurement
Control External Procurement
- For talbe V_T160PR, profile and corresponding SRM systems can be maintained.
Customizing path:
SPRO->..
SAP Customizing Implementation Guide
Integration with Other mySAP.com Components
Supplier Relationship Management
Plan-Driven Procurement
Maintain Profiles for External Procurement
3. Procurement profile can't be re-determined with t-code ME54N, ME54 or ME55.
Sometimes, end users want to change purchasing group or material group to update the EPROFILE in purchase requisition. This can be realized with t-code ME52N or ME52.
However some end users directly use t-code ME54N to change this before releasing the PR. This won't update the EPROFILE in EBAN and EPRTRANS tables.
Reason: This is hard-coded in function module BBP_EPROFILE_REQ_CHANGE
You may also refer to KBA note 1964977.
