Skip to main content

Vendor List based on Creation Date

Ideally, Vendor list can be displayed through T.Code - MKVZ where we can fetch vendor list either at Purchase Org or Account group or Generic.

Below is the list of fields we can fetch through this.

Name of vendor
Street
Country
Postal Code
City
Account group
Search term
Central purchasing block
Block function
Central deletion flag
One-time account
Purch. Organization
Purch. Org. Descr.
Terms of Payment
Incoterms
Incoterms (Part 2)
Purch. block for purchasing organization
Delete flag for purchasing organization
Minimum order value 0
Order currency
Salesperson
Telephone
Reference Purchasing Org.
Number of Purchasing Organizations 1

But at times business requires to fetch vendor list based on creation date. This cannot be accomplished through the above T.Code instead SAP has given T.Code S_ALR_87012086 to fetch the data.





Thank you.

Comments

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

Determinations in SAP SD

Plant Determination in Sales Order 1st Preference: System fetches Delivering plant from Customer Material Info Record if Plant is not found at this level then system will look into 2nd Preference:   Delivering plant from Customer Master data if Plant is not found at this level then system will look into 3rd Preference : the Delivering plant for Material Master data If business user overwrites Plant at sales document level then this will be given highest preference. Shipping Point Determination Delivering Plant (Based on above conditions) + Shipping Conditions ( Sales Document Type or  Customer Master Data) + Loading Group ( Material Master ) Storage Location Determination Plant + Shipping Point + Storage Conditions ( Material Master )  ( MALA) Plant + Shipping Point + Situation  ( RETA) Route Determination Departure Zone or Country of the Delivering Plant + Destination Zone or Country of the Ship to Party + Shipping Condition from the Customer Master + Transport