-
Integration
- 7900 - The ITR isn't integrated into the YDB DB
- 7902 - The ITR isn't integrated into the MEW DB
- 7928 - Outgoing isn't integrated into YDB DB
- 8073 - PO>>ITR, IT>>GRPO doesn't integrated into all databases
- 8101 - Item Code has not been integrated into MEW DB
- 8112 - Please Resolve the Issue with ITR closing failures
- 8299 - GRPO isn't integrated into SHI DB
- 8329 - The ITR has not been integrated into other databases
- 7834 - Inventory Transfer API Issue (urgent)
- 7845 - Please Check & Resolve Incorrect Sale Integration Error Log
- 7852 - The ITR isn't integrated into the MMF DB
- 8313 - Customer Code Mapping
- 8314 - Price Change Integration ပိတ်ရန်ကိစ္စ
- 8334 - Please Check the delay in the integration of AR invoices into B2B
- 8414 - Please Check & Resolve Incorrect Sale Integration Error Log
- 8075 - Sales data integrated from SHI does not match with YDB DB
- 8078 - Product Integration Announcement
- 8121 - Item Codes have not been integrated into SHT DB
- 8218 - Sales Integration မဆင်းနေသောကြောင့် စစ်ဆေးပေးစေလိုခြင်း။
- 8248 - Please resolve the issue of ItemCodes with price changes don't imported from SAP to Za
- 7903 - SLD down သွားချိန်အတွင်း Integration များ Check ရန်
- 7911 - GRPO isn't integrated into SHI DB
- 8436 - Item Code has not been integrated into MEW DB
- 8270 - New Branch (Pyinoolwin) Creation in SAP
- 8276 - UDF
- 8278 - Integration Monitor
- 8298 - OITW.AvgPrice
- 8327 - YWHROKS9 သည် Sales Integration ဆင်းမနေခြင်း။
- 8354 - Incoming data integrated from SHI does not match with KCC DB
- 8212 - Error Code - 5002
- 8229 - SAP to DW
- Show Remaining Articles (16) Collapse Articles
Table of Contents
< All Topics
Print
8313 – Customer Code Mapping
Issue Summary: [8313] Customer Code Mapping issue with incorrect customer code group and mapping sheet in SH to Other DB, causing integration errors.
Resolution / Workaround: The support team created a ticket (8313) for the issue. After investigation, it was found that the customer code mapping was done on April 5th, but the integration run only occurred on May 2nd. The team suggested running the integration with backdated data if necessary to resolve the issue.
