Data Disclosure 

Use

File System

If you have formatted data and created IDocs for a store, the system creates a trigger file. This contains the following information:

●     that data is ready for the POS system to collect

●     the names of the individual data files (IDocs)

●     where the data is located

The Store Connection System (SCS) can then begin processing the data for the store concerned.

Logical Systems

If IDocs are passed on directly using Remote Function Calls (RFC) rather than via file ports (distribution using logical systems and distribution model), the system does not normally create a trigger file since no file ports can be specified for this type of distribution.

However, you can still send this trigger information using RFC. This is particularly important if intelligent POS systems that are able to understand the IDoc information straight away without converter software are used. In this case, you simply require a transfer tool that transfers the data to the POS server.

Integration

File System

POS interface – outbound creates the trigger file in the directory path that is defined in the port descriptions for the status files.

When you maintain partner profiles for each store and message type, you can maintain a different port description. However, you must ensure that you either use only one single port description, or that at least the outbound files in the port descriptions that are used are defined the same.

Logical Systems

The POS interface outbound sends the trigger information to the RFC destination of the same transactional RFC port to which the relevant IDocs are also sent.

Prerequisites

●     The directory path for the trigger file must be the same for the whole of POS outbound.

●     Both the SAP system and the POS converter must have access to the directory.

Features

When data is prepared for POS outbound as a result of initialization, the change message or direct request, the system can issue the following messages:

●     Trigger file did not need to be created

This message is issued if:

○     The status record concerned is currently blocked.

This can happen if the help program, RWDPOSTG is also started, but this is only likely to happen in exceptional cases. In this case, this program creates the trigger file. This means that the data is still transferred.

○     No IDoc was created.

This can only happen if no data for is available for preparation for this store, or the data that was to be prepared led to preparation errors. You must check the error log.

○     No IDoc with status 03 (transfer to port OK) was created.

This is caused by an error in the ALE layer. One reason for this error could be that no outbound parameters have been created for this store in the ALE layer. You must correct the error in the ALE layer and restart the preparation program.

●     Trigger file could not be created

The errors that lead to this message are recorded in a general log for POS interface - outbound. You can display this log by choosing Goto ® General logs.

File System

The nomenclature of the data files (IDocs) can be set in Customizing for port definitions (transaction WE21) in the ALE layer by selecting or creating a suitable function module.

Logical Systems

When using distribution via logical systems, Customizing relating to this is not possible as no files are created in this case, just data streams.

Therefore, the trigger information sent via RFC receives the name of the trigger file to be saved on the POS server and the name of the IDoc files already saved there.

The latter can only be true if the same nomenclature as in the trigger information is used when saving the IDoc files.

The nomenclature is already predetermined and is generated as follows from the information in the IDoc control record:

<the first 10 characters of the message type>_<the last 9 digits of the IDOC number>.xml

Activities

Normally, the system automatically creates trigger files during POS outbound processing. If, however, a trigger file could not be created for the converter (because there was insufficient disk space, for example), you do not need to repeat the formatting. You simply need to start program RWDPOSTG once you have corrected the cause of the problem. It checks whether any data still needs to be prepared for which no trigger file was created. If the system finds formatting like this, the program generates the relevant trigger files. Before you call this program, you must run a reorganization of the POS interface.