SAP Vistex Process – Key Identifiers and their usage in Create Master Data

Identifiers:

• Identifiers are used on a daily basis for Program determination, BADIs, Tables etc. It is an easy way to determine which part of the team is responsible for a problem identified in the Vistex. Below identifiers are used for Vistex  system

PD – Item

LI – Vendor

KU – Customer

Identifiers usage in Tables :

Customer

Table Name                     Short text

/IRM/EPKUACT                   Customer – Actions

/IRM/EPKUATV                   Customer Attribute Values

Material

Table Name                     Short text

/IRM/EPPDACT                   Material – Actions

/IRM/EPPDATV                   Material Attribute Values

Vendor

Table Name                     Short text

/IRM/EPLIACT                   Vendor – Actions

/IRM/EPLIATV                   Vendor Attribute Values

Product Types: Table Name: /IRM/TEPPDTYP

Vendor Types:Table Name: /IRM/TEPLITYP

Customer Types:/IRM/TEPKUTYP

Create, Change & Update Data:

Below are the three different transactions which are used to Create, change and update data in the system.

• Workbench
• List Workbench
• Dashboard

WORKBENCH: Used for creation and change-

• Item or Material workbench – T Code     /IRM/EPPDM
• Reference material used to create a new material is mentioned under ‘General’ tab.
• The creation/Change/Update of data in Vistex is under the scope and responsibility of another team known as EDM team.
• EDM team are the end users who manipulate the Vistex data.
• Some info for creating a new material are loaded using the rules in the Vistex system via the Rule Workbench.
• New Attribute values can be inserted along with the existing ones with a new effective date. This is always suggested.
• Effective date is always setup to the next business date.
• Effective date is very critical during the Syndication process or interfacing to the downward system.
• For Pharma items, there is an index table. Index table has all the data related to changes/creation. This data will be picked at 1800 hrs. PST as part of daily syndication and stored in the flat file.
• This flat file updates ECC.
• For Specialty items, in EP1, an IDOC is created when an item is created.
• McKesson don’t have any Template material. They use only Reference Material.

LIST WORKBENCH: Used for creation and change-

• Material List Workbench – T Code /IRM/EPPDLM
• List Types used for Pharma Items – CHOT, CHRX, CROT, CRRX (XXOT- OTC Item, XXRX – RX item)
• List Types used for MSH/Specialty Items – ZMP1, ZMS2, ZMS1, ZMS3, ZMS4
• Save – It only saves the info in the List Tables, creates an internal number for the list.
• Save Post – It saves the info in the List Tables and also post it into the Vistex system. This action completes the change/creation of new material. Once it is posted, this info can only be discarded if any change is needed to it.
• Difference between Workbench and List Workbench – These are only two different ways of creating/modifying the data. There is not much difference. While supporting the system, we mostly use Workbench whereas Users are trained to use List Workbench.

DASHBOARD: Used for change & update the data massively

• Used for mass updates – several attributes for several items can be updated at a time
• Material Dashboard – T Code /IRM/EPPD10
• Similar to Workbench
• Used only for change, No creation

In the above processes, by putting KU in place of PD we can able to complete the Customer Process

By putting LI in place of LI we can able to complete the Vendor Process.

Above one is purely based on my experience as I got couple of P1 Tickets where time is very critical to resolve in my Previous projects and by following the above mechanism able to resolve those issue in a very quick turnaround time, I believe this will be helpful for others who are facing similar issues hence though to share my experience by posting this blog

Please let me know to explain in pictures if required.

Thanks, Sreeram