POS Outbound Profile (SAP Library - POS Interface

POS Outbound Profile

Use

You will already have made a great deal of the settings required for POS outbound processing when setting up your POS outbound profile. Together with the EDI partner profile and the activation of ALE message types, it controls the data flow of message types to stores.

A POS outbound profile can be used simultaneously for many sites, as the information contained in it relates to the location and the POS system.

Integration

The following fields affect POS outbound:

Field name	Description	This means:
VZEIT	Store lead time	Determines how many days the POS interface – outbound formatting should last. A lead time of 2 days, for example, determines that the data for today and tomorrow, in other words, a day in advance, should be formatted and sent.
KURST	Exchange rate type	Key under which the exchange rates for currencies are stored in the system.
EKOAR	Condition type group	Identifies a condition type record whose condition types were analyzed in outbound processing and transferred to a POS system. If this field is empty, then prices cannot be determined or transferred.
MEPER	Reduced message type for personnel master	Logical message type for reducing the personnel master IDoc structure. The reduction must be created in the ALE environment. The structure information from the reduced IDoc structure is used for formatting the data. If the system no longer has to read entire tables, the performance improves. If the field is empty, the intermediate document is not reduced which means the whole personnel master is transferred.
MESTYPE_PLU	Reduced message type for article master	Logical message type for reducing the article master IDoc structure. The reduction must be created in the ALE environment. The structure information from the reduced IDoc structure is used for formatting the data. If the system no longer has to read entire tables, performance is improved. If the field is empty, the intermediate document will not be reduced, which means the whole article master is transferred.
OKSTA	Status communication successful	IDoc status for which the communication is determined as being successful. This status should be set to the last value that the destination converter or the recipient POS system can send as a status message to the SAP system if the communication is successful. The value should not be 18 (EDI subsystem initialization OK) if the POS interface – outbound has to be restarted. The system cannot recognize which of the IDocs that were already transferred to a destination converter have already been processed.
RECDT	Recipient determination	Indicator that should be used to determine recipients using the distribution model when IDocs are being created, even if recipient-specific information is being formatted. The procedure has the following advantages: An IDoc can be sent to several logical systems. For each message type specific logical systems of the recipient can be addressed. A prerequisite is that logical systems are entered as recipients in the ALE distribution model for the message types concerned. Recipient-specific messages can be assigned to different recipients using filter objects.
ERMOD	Error handling	If there are items containing errors in POS outbound, this defines either That the outbound program is terminated (indicator set) or The items containing errors are logged and the outbound program continues with the next items.
POSDEX	Automatic data exchange with the store	Indicator for supplying data to and removing data from the POS systems in the store. If the indicator is not set, then the POS outbound profile is only used for controlling the assortment list.
SALLMG	Sales allowed for all merchandise categories	Indicator for formatting all merchandise categories for POS outbound and not only those that are assigned to the store that is to be formatted.
EAN_ART	Cross-link articles and EAN references	Indicator for linking the message for the EAN references to the message for the article master when relevant master record changes are being analyzed in POS outbound. A change to an additional EAN leads to the article master being formatted too. Equally, formatting an article leads to the EAN references being formatted (if a change is being made). This indicator should be set for POS systems that cannot carry EAN references and require instead the complete article master message for all EANs.
EAN_DEL	Additional deletion records for EAN records	Indicator that sends an additional deletion record (WP_EAN01) with the deleted EAN as the main EAN to the POS system when deleting an additional EAN. Some older POS systems cannot maintain a connection between the main EAN and the EAN references. These POS systems require additional deletion records.
FOA_ART	Cross-link follow-on item and article	Indicator that a change relevant to a bill of materials for empties not only leads to formatting the message for the follow-on item, but also to formatting the article master belonging to it. This indicator should be set for POS systems that cannot retain the relationship of the BOM for empties components as separate data, but always require the complete article master.
MCAT_ART	Send merchandise category article	Indicator that a data record for the article master message is also to be formatted in POS outbound for the merchandise category article. This is only necessary if the information that is sent with the message for the merchandise categories is not sufficient.
NPMAT	Do not format article master data	Indicator for generally preventing article data being formatted (including EAN references) in POS outbound processing.
NO_BONTEXT	Do not format POS receipt texts	Indicator for preventing POS receipt texts being formatted for the article master message in POS outbound. This can improve performance if the POS receipt texts are not required in the POS systems. You cannot remove POS receipt texts separately by reducing the article master IDoc.
NPFOA	Do not format follow-on items	Indicator that follow-on item data should generally be excluded from formatting in POS outbound processing.
NPSET	Do not format sales sets	Indicator that sales set data should generally be excluded from formatting in POS outbound processing.
NPMEC	Do not format merchandise category data	Indicator that merchandise category data should generally be excluded from data formatting in POS outbound processing.
NPCUR	Do not format exchange rates	Indicator that exchange rates should generally be excluded from formatting in POS outbound processing.
NPTAX	Do not format tax rates	Indicator that tax rates should generally be excluded from data formatting in POS outbound processing.
NPCUS	Do not format customer data	Indicator that customer data should generally be excluded from data formatting in POS outbound processing.
NO_FABKL	Do not use logistics calendar	Indicator that the logistics calendar is not taken into account in POS outbound. POS outbound processing will then work on the basis that every day is a working day.
PROMO_REBATE	Format promotion discount	Indicator that the system is using a separate IDoc type to format special promotion discounts that are maintained on levels higher than the article level. Set this indicator if you want the system to format promotion discounts like this. Discounts referring to an entire merchandise category or a whole assortment are transferred to the IDoc type. It is worth using this indicator if the target system in the store can evaluate the information that was formatted in this IDoc. This generally only applies to store retailing systems, as POS systems are mostly dependent on article-specific information. The target system must expand the incoming discount information at article level and transfer it to the POS systems.
PRICING_DIRECT	Read prices directly (performance)	Indicator for reading the price information directly. A large part of the POS outbound runtime is taken up by pricing. The reason for this is that a large part of the runtime is needed for interpreting the calculation schema and the flexible pricing according to the calculation schema that is being used. If the indicator is set, the system determines the price information that is required directly. To allow you to use this procedure, the condition types that are listed in the condition type group in POS outbound fulfill one of the following conditions: The condition type is a main condition type (has an access sequence). The delivered condition types VKP0 and VKA0 are examples of condition types for the normal sales price and the promotion price. The condition type MWST is also used for the value-added tax. The condition type is an additional condition for a main condition used in POS outbound. An example of a delivered condition type is VKP1 that is an additional condition type for the main condition type VKP0. The condition type has a main condition type as the reference condition type. An example of this is the delivered condition type MWSI that is a reference condition type with the main condition type MWST assigned to it. The condition type has the condition category G, S or T. The delivered condition type VPRS is an example of this. This procedure cannot be used if Certain values are calculated in the calculation schema. The lowest price could be calculated from two or more prices. Scale prices are used.
PRICES_SITEINDEP	Prices independent of store (performance)	Indicator that the article prices of all the stores that use this POS outbound profile are maintained separately from the store. If you set this indicator, then the prices can only be saved at client level or distribution chain level. The POS outbound change function reacts to this indicator not by constantly calculating the price information for each store again, but by temporarily storing the prices internally that have already been calculated so that they can be used again when formatting other stores in the same program run. Information from the condition analysis is also stored temporarily and used again for formatting the rest of the stores. This improves performance. Store-dependent prices would lead to inconsistencies in formatting. Prices that are stored at price list type level (table A006) or at promotion level (table A954) that may also have store grouping assignments are also store-dependent and therefore do not require this indicator to be set.
PRICES_IN_A071	Store-dependent prices in A071 (performance)	Indicator that all store-independent prices are located in table A071. Like the indicator Store-independent prices, store-independent information on prices is copied here instead of having to be recalculated every time. If you set this indicator, store-dependent prices can be maintained. However, this is only the case for standard delivery condition table A071. Only a proportionally small fraction of the prices (up to approximately 10%) should be store-dependent. This improves performance greatly. Information from this condition analysis cannot be stored temporarily here.
NO_WARNINGS	Warnings should be declared as notes	Indicator that warnings should be declared as notes. If a data record cannot be formatted during data formatting in POS outbound, then the entire download is registered as containing errors and it has to be repeated. This is only the case if the formatting is not repeated using the POS monitor. If you set this indicator, the header line status is changed from Note to Warnings. This way, the whole download achieves status OK and it does not have to be repeated. In the POS monitor, the download is displayed under the category Processed instead of Processing incomplete. The IDocs, which contain errors, are still flagged as containing errors. This way, the error logs can still be displayed. If you set this indicator, you should definitely check the downloads in the POS monitor that have a Note and correct any errors that occurred. Warning: If serious errors occur during the formatting, where a whole IDoc could not be formatted, then these will not be changed into a Note.
TAXES_COPY	Copy tax code in variants	Indicator that the value-added tax is to be copied for all the variants in the same generic article. If you set this indicator, it affects the algorithm in POS outbound so that the tax code is not redefined for every variant in a generic article. Instead it is copied internally. This increases performance. Background: You can maintain different tax codes for every variant in a generic article and for this reason the POS outbound has to redefine the tax code every time. Set this indicator if you use the same tax code for all the variants in the same generic article.
NO_TRIGGER	Do not create a trigger file	Indicator that a trigger file is not to be created. If you set this indicator, a trigger file will not be created during formatting in POS outbound. This is necessary if, for example, data is to be distributed using the distribution model (indicator Recipient determination). In this case, the program sets the indicator if it has not already been set. However, there are distribution scenarios where data is not to be distributed using the distribution model and no trigger file is needed. The data could be distributed using a Business Connector. Set the indicator for cases like this.

Activities

Maintain the POS outbound profile in the Implementation Guide (IMG) in the Sales and Distribution area under POS Interface ® Outbound ® Maintain Profile For POS Outbound.

If you have created the POS outbound profile, enter the name of it in the site master record for the store. This provides the connection between the store and the data for outbound processing.