POS Data Processing One-Step Tasks – Test Administration Customer project: Fill in the project-specific parts (highlighted). Test Case ID <X.XX> Tester Name Testing Date Click here to enter a date. Responsibility Service Provider, Customer or Joint Service Provider and Customer> Duration 10 Minutes Purpose Tasks are operations on the POS transaction data. The following types of tasks exist: Supplying follow-up systems such as SAP BW or SAP ERP with POS data. Tasks carried out externally or manually that can be recorded in the PIPE. An example of this would be the sales audit, which can be mapped as a task. The sales auditor can then record the task in the PIPE. Performance-intensive checks that are too performance-intensive for For such checks it makes sense to store the result as the status of the task. The tasks have a status that indicates whether they are completed, incorrect, cancelled or refused, and so on. Procedure Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment Log on Log on the SAP Customer Activity Repository system Switch to User Menu Click User Menu Run POS Data Parallel Processing User Menu > POS Processing > POS Data Parallel POS Data Parallel Processing completed Processing (transaction /n/POSDW/PDIS) successfully Task Code: enter CT10 (Check for Receipt Numbers Without Gaps), choose to select further tasks: PT09 (Create IDOC WPUBON), PT12 Generate IDOC WPUFIB), choose Execute.
POS Data Processing – One-Step Tasks Test Administration Customer project: Fill in the project-specific parts (highlighted). Test Case ID <X.XX> Tester Name Testing Date Click here to enter a date. Responsibility Service Provider, Customer or Joint Service Provider and Customer> Duration 10 Minutes Purpose Tasks are operations on the POS transaction data. The following types of tasks exist: Supplying follow-up systems such as SAP BW or SAP ERP with POS data. Tasks carried out externally or manually that can be recorded in the PIPE. An example of this would be the sales audit, which can be mapped as a task. The sales auditor can then record the task in the PIPE. Performance-intensive checks that are too performance-intensive for For such checks it makes sense to store the result as the status of the task. The tasks have a status that indicates whether they are completed, incorrect, cancelled or refused, and so on. Procedure Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment Log on Log on the SAP Customer Activity Repository system Switch to User Menu Click User Menu Run POS Data Parallel Processing User Menu > POS Processing > POS Data Parallel Processing (transaction /n/POSDW/PDIS) Task Code: enter CT10 (Check for Receipt Numbers Without Gaps), choose to select further tasks: PT09 (Create IDOC WPUBON), PT12 Generate IDOC WPUFIB), choose Execute. POS Data Parallel Processing completed successfully
R72_CARAB20_BPD_EN_XX.docx