price catalog

[Former Member]

hi can any explain me about the price catalog thing which we find under edi messages

spro>sales and distribution>>edi messages>> price catalouge

and if any knows the full procedure how to do with transaction codes and wat it is exactly kindly help me

thanks

[Former Member]

Hi Priti,

EDIFACT (Electronic Data Interchange for Administration Commerce and Transport) is a cross-industry standard for exchanging formatted, structured data. EDIFACT messages can be combined with application guidelines to cover specific requirements (= subset).

EANCOM is an EDIFACT subset with detailed implementation guidelines of simplified EDIFACT messages. EANCOM covers all the main business transactions in the whole consumer products industry.

PRICAT is an EANCOM standard message type relating to master data. PRICAT enables pricing and catalog-related data for goods and services to be transferred from a vendor to a buyer. It contains

A complete list of products

Notification of changes

Information for all customers

Customer-specific information

Data supplied to a central article database

SINFOS is a message format for transferring article master data. The CCG (Central Office for Coorganization) holds the article master data of German, Austrian and Dutch traders centrally in a ‘SINFOS pool’. Data is supplied to the SINFOS pool using PRICAT messages.

There are therefore two important factors regarding the processing of PRICAT messages:

Transfer of data to SINFOS pool (or other master data pools):

Reading of pool data (price catalog inbound)

Transfer of own articles to data pool (price catalog outbound)

B2B: Transfer of a price catalog from a vendor to a customer:

Vendor sends article data to the customer (price catalog outbound)

Customer receives article data from the vendor (price catalog inbound)

In R/3, data is exchanged using PRICAT with the IDoc PRICECATALOGUE. This IDoc contains all the necessary information. An EDI subsystem can convert this IDoc into a PRICAT message immediately.

As transfer using SINFOS is a special case that is not relevant in all cases, the B2B case will be demonstrated here. (Data is supplied to the SINFOS pool using the method described for price catalog outbound. Article data is downloaded from the SINFOS pool using the method described for price catalog inbound.)

To be able to demonstrate the whole B2B case on a single system, we will use the following scenario.

A vendor, PCS-V411, who has company code PS0L and distribution chain V00L V3 supplies customers PCS-C300 and PCS-C399 who have company code PS0K and distribution chain V00K V3.

For price catalog outbound, we will assume the role of the vendor, who creates a price catalog using transaction VPRICAT and sends this. This results in an outbound IDoc of type PRICECATALOGUE, which is sent via the PCS-RFC port. However, the PCS-RFC port refers to its own IP address, so an inbound IDoc is also created immediately in the same system. When a catalog is sent, therefore, an inbound and outbound IDoc are created for each customer.

We are now at the inbound processing stage, and therefore assume the role of the customer. Processing of the inbound IDoc results in the creation of a price catalog, which we process using transaction PRICAT. Transaction PRICAT is used to decide whether and how each new article in the price catalog is created, or whether the existing article for which a change is reported is updated.

http://help.sap.com/bp_retailv1470/documentation/EN/Price%20catalog_EN_CUST_V147.doc

Reward points if u helpful

Cheers

Govind.