Child pages
  • PO Vendor Flags
Skip to end of metadata
Go to start of metadata

Purpose

This is to explain the standard behavior and trouble shooting hint of the PO Vendor Flags.

Overview

In this article you will understand standard behavior and trouble shooting hint of the PO Vendor Flags.

Standard Behavior

1    Create Scenario

All the vendor flags in UI are editable

Vendor Assigned + Default purchase organization

Case1 - Adding a new item

While adding a new item, vendor flags should be inherited from vendor master based on vendor and purchasing organization combination

Case2 - Modifying vendor flags for existing items

On manipulating the vendor flags manually, user entered flags should be retained(Only first time flags are inherited from vendor master, after manual changes of flags by user, it will never be overwritten by vendor master )

 

 


 

Vendor assigned after adding item

Case1 - Flags are changed manually by user for any item before adding vendor

After adding vendor the flags should not be overwritten by vendor master for existing items

After adding a vendor - While adding a new item, vendor flags should be inherited from Vendor master based on vendor and purchasing organization combination

Case2 - Flags are not modified by user for any item before adding vendor

While adding a new item, vendor flags should be inherited from Vendor master based on vendor and purchasing organization combination

On manipulating the vendor flags manually, user entered flags should be retained(Only first time flags are inherited from vendor master, after manual changes of flags by user, it will never be overwritten by vendor master )

 

 

 

 

 

 

 

Vendor changed after adding item

Case1 - For existing items

Vendor flags should not be overwritten with the change of vendor

Case2 - For newly added item

While adding a new item, vendor flags should be inherited from Vendor master based on vendor and purchasing organization combination

 


 


 

Change of Purchasing Organization before adding item

Case1 - Adding a new item

While adding a new item, vendor flags should be inherited from Vendor master based on vendor and purchasing organization combination

Case2 - Modifying vendor flags for existing items

On manipulating the vendor flags manually, user entered flags should be retained(Only first time flags are inherited from vendor master, after manual changes of flags by user, it will never be overwritten by vendor master )

 

 



 

Change of Purchasing Organization after adding item

Case1 - For existing items

Vendor flags should not be overwritten with the change of Purchasing Organization

Case2 - For newly added item

While adding a new item, vendor flags should be inherited from Vendor master based on vendor and purchasing organization combination

 



 

For Services and Limits in Extended Classic Scenario

Case 1 - IF the vendor flags -  Goods Receipt / Confirmation of Performance of Service Flag &  Invoice Expected Flag  are checked  and  Confirmation-Based Invoice Verification Flag is unchecked ((Manually or Vendor Master)

If  Goods Receipt / Confirmation of Performance of Service Flag and Invoice Expected Flag are checked  and  Confirmation-Based Invoice Verification Flag is unchecked then the  Confirmation-Based Invoice Verification Flag should be set manually

Case 2 - IF the vendor flag -  Invoice Expected Flag is checked,  Goods Receipt / Confirmation of Performance of Service Flag is unchecked  and  Confirmation-Based Invoice Verification Flag is unchecked ((Manually or Vendor Master)

Confirmation-Based Invoice Verification Flag and  Goods Receipt / Confirmation of Performance of Service Flag need not be set

Case 3 - IF the vendor flag -  Goods Receipt / Confirmation of Performance of Service Flag is checked  and  Confirmation-Based Invoice Verification Flag is unchecked ((Manually or Vendor Master)

Then  Invoice Expected Flag and  Confirmation-Based Invoice Verification Flag can be set manually

 

 

 

 

 

 

 

 

 

 

2    Change Version

If follow on document does not exist

Case1 - Modifying vendor flags for existing items

Manipulation of Vendor flags should be possible for existing items

Case2 - For newly added item

While adding a new item, vendor flags should be inherited from Vendor master based on vendor and purchasing organization combination

If follow on document exists

Case 1 : If only Confirmation exists  

then Goods Receipt / Confirmation of Performance of Service Flag should be non-editable but Invoice Expected Flag and Confirmation-Based Invoice Verification Flag  should be editable

Case 2 : If Invoice exists  

then Invoice Expected Flag and Confirmation-Based Invoice Verification Flag should be non-editable

Case2 - If try to modify Confirmation-Based Invoice Verification Flag  when Invoice already exists

Confirmation-Based Invoice Verification Flag should be non-editable

Case3 - If Confirmation-Based Invoice Verification Flag is modified and only Confirmation exists

Changes to Confirmation-Based Invoice Verification Flag should be allowed

Case4 - If confirmation or invoice exists, changes to Purchase Order Response  Flag and Shipping Notification Flag

Modification of Shipping Notification Flag , Purchase Order Response  Flag should not be allowed

Case 5 : If only Confirmation exists  

For Extended Classic PO, although IR and GR based IR are editable, the system will not allow to uncheck these flags.

 

 

3   Impact of Document Data on Vendor Flags

Conditional Flow

Purchase Order Response Flag

Shipping Notification Flag

Goods Receipt / Confirmation of Performance of Service Flag

Invoice Expected Flag

Confirmation-Based Invoice Verification Flag

Evaluated Receipt Settlement Flag

Evaluated Receipt Settlement  Flag Checked(Manually or Vendor Master)

Depends on Manual/Vendor Master

Depends on Manual/Vendor Master

Checked

Checked

Checked

Checked

Goods Receipt / Confirmation of Performance of Service Flag, Invoice Expected Flag is unchecked(Manually or Vendor Master)

Depends on Manual/Vendor Master

Depends on Manual/Vendor Master

Unchecked

Unchecked

Unchecked

Unchecked

Procurement card Exists

Depends on Manual/Vendor Master

Depends on Manual/Vendor Master

Unchecked

Unchecked

Unchecked

Unchecked

 

Commonly asked question

1, Gr_based IV is removed if either GR and IV flag are off. This is standard behavior because of the the definition.

2, If ECC flags are not set as editable in the customizing, the flags are not transferred , this is standard behavior of MM BAPI.

Function and programs

Follow on document flags determination
Include LBBP_PDBUPF2D / fill_ecom reads the flags from the vendor master data
Include LBBP_PDIGPF0B / po_itm_check reads the confirmation/invoice values from the backend
document (in extended classic scenario)
Include LBBP_PDIGPF75 / check_iv_gr_flags carries out the main steps for determining whether the flags are
set or not Related SAP Notes/KBAs

Related Content

Related SAP Notes/KBAs

KBA: 1718228 Collection notes to known issues related to GR_BASEDIV flag

SAP Note: 1771316  Inconsistent behavior of Vendor flags in Purchase Order

SAP Note: 1788400  Inconsistent behavior of Vendor flags in Extended Classic PO

SAP Note: 1758626 POR flag not mapped from Vendor Master to the Purchase Order

SAP Note: 1796775  GR_BASEDIV set for material item irrespective of vendor data

SAP Note: 1789631  Issues in vendor flags of limit items in Purchase Order

SAP Note: 1793015  GR_Basediv for Limit and Service items

SAP Note: 1806699  GR_BASEDIV flag not set for services in Extended Classic

SAP Note: 1786941  Some vendor flags are not set during creation of PO from SC

SAP Note: 1869819  Flags set in limit SC in not considered during PO creation

SAP Note: 1828837  GR_IND is set in PO items which is created from SC

SAP Note: 2043399  GR and IR flags are not set for PO with service items.

SAP Note: 2311605  Follow-On Document Indicators not Defaulted2311605 - Follow-On Document Indicators not Defaulted

SAP Note: 2414914  BBP_DOC_CHANGE_BADI follow-on document flags set on SC are not copied in to follow-on PO

SAP Note: 2534087  ERS flag not set when ERS vendor added to draft after SOCO

 

 

1 Comment

  1. Hello,


    just one precision regarding 'Evaluated Receipt Settlement' SRM PO item flag (Extended Classic scenario for Material item type):

    1) if SRM Vendor Master data has this flag set, you can unset it in PO item flag and then order the PO,

    2) if SRM Vendor Master data has this flag unset, you can set it in PO item flag, but when ordering the PO, you will have error message BBP_PD 156 (Supplier &1 is not permitted for automatic settlement) from include LBBP_PDF2Z.

    Regards.


    Laurent.