![]() So that qRFC applications can still process their queues themselves, the QIN Scheduler will only start queues that are already registered. Since inbound queues are “only” described for both applications on the same system and in remote systems (also possible from external systems via the RFC library) and therefore every application would almost have to provide the same work for the queue activation, qRFC also provides the QIN Scheduler that has the task of activating as many inbound queues (not outbound queues) as possible using the current system resources. – How should the resources for QIN Scheduler be configured? – How can blocking queues be activated again? – How can you debug the execution of a registered queue? ![]() – Which client/user/language is used to execute a qRFC-LUW? – How are registered inbound queues activated? – What is the meaning of the different statuses of a QIN Scheduler? – How does one recognize the status of a QIN Scheduler? – When does a QIN Scheduler become active? – How can inbound queues be registered/deregistered? We need check IDOC created on ERP |S4 also green to make sure that sales and payment created business transaction.– How many QIN Schedulers are there in a system? SAP CAR will send to SAP ERP | S4, status is green mean data transferred to SAP ERP | S4. ![]() Transaction will be aggregated by Business Date / Store or follow your custom logic. In the common process, SAP CAR will send sales and payment aggregated to SAP S4 through two basic type: Transaction checked on POS Workbench with success indicator will be transfer to SAP ERP and SAP BW.īackground job program: /POSDW/PIPEDISPATCHER + Error with balanced audit check, example, sum of sales not equal with payment.ĭepend on issue then we need to make decision whether will be fixed. + Error with master data check, example, in some scenarios, POS sent to CAR some items with material don’t exist on SAP CAR. There are two kind of error message you need to consider For production system we have to run background jobs to execute tasks.ĭata sent to POS workbench, master data will be audit by tasks or another tasks depend on your CAR setting up.ĭetail error of each transaction will show on “Message” tab TCode: /POSDW/MON0 You can filter transactions by status of tasks or transaction typesįor testing purpose we can perform task manually for each transaction. Tasks aggregate sales, payment and send raw data to SAP BW will be execute by manually. Some tasks on “POS workbench” perform immediately, some are need to process by background job or manually.Įxample, task to check duplicate transaction or check balanced transaction will be executed immediately. For production system, inbound queue have to processed by background jobs.īackground job program: /POSDW/INBOUNDDISPATCHMON When background jobs run, we need to make sure that all inbound data processed and no record show on “Inbound Queue” 3 – Check POS Workbenchĭata processed from “Inbound Queue” will be send to “POS workbench”. In the technical perspective, i think it will help administrator split data and reduce huge data processing in the same time on CAR.įor testing, we can process inbound queue manually. ![]() As business requirement, convenient store’s data need to process and transfer to SAP ERP first, user want to check inventory first… then we perform process those stores from queue first. Example, customer has thousand of stores, there are F&B stores and convenient stores. Data put to queue to help us control priorities of data processing. I am not sure why SAP did it, in my opinion SAP CAR designed for multi-channel and business. The question is why we need Inbound Queue ? IDOC created on IDOC workbench will send to inbound Queue Monitor. ![]() SAP CAR will validate and raise error, detail error will show when you click on error IDOC Example issue, missing partner profiles on SAP CAR 2 – Inbound Queue Monitoring In some scenario, partner system sent wrong IDOC structure or logic of data. TCode: WE02 Make sure that all inbound sales idoc are green When you send sales data to SAP IDOC with basic type: /POSDW/POSTR_CREATEMULTIPLE04, you need to make sure that there are no technical issue with inbound IDOC. In picture below, i putted common standard inbound sales receipt to SAP CAR. Let’s assume that data was transferred success through integration middle-ware. In this tip, i only show you guys how to monitor inbound sales receipt from partners system only. There are several parts of data transfer from legacy system to SAP CAR POS DTA depend on your integration landscape is.Įxample, if in your landscape have integration middle-ware like SAP Process Integration, SAP Process Orchestration, Mulesoft, etc… then you need to check sales inbound of each point. In this tip i will show you step by step to do SAP CAR POS DTA (Point of sales data transfer and audit) monitoring. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |