On a weekly basis an external system is providing all product and price information to the customer. These are always all 200,000 records as the external system is not able to create delta information although typically only around 50 changes may be involved. Also deleted items are not visible because you will just no longer find them in the file. The data is provided in an excel sheet. The product information in SAP B1 needs to be updated. In addition all new product information has to be sent to the customer’s e-shop.
We create a new B1iSN integration step. The inbound is SAP B1 event triggered. In the inbound phase we define a Key Expansion to additional extract data, related to the linked business partner object information. This key expansion is just a definition in B1iSN. The transformation of the enriched B1 purchase order is placing the B1 order number into the R/3 field for the external key. The R/3 is configured to send out sales order changes to the B1iSN (to be defined as a logical system in R/3). This guarantees that immediately after insertion in R/3 an IDOC is sent out to B1iSN, covering the R/3 sales order including the generated R/3 order key. B1iSN as an RFC server is receiving the IDOC and triggers a second integration step which transforms the data and sends it to SAP B1, identified by the B1 primary key, sent by R/3 as the external key. Now you have in both systems the both primary keys of SAP B1 and SAP R/3. After a while the delivery notification is created in R/3. Also here the R/3 needs to be configured to send it out to the B1iSN server. A third integration step is converting this notification and handing it over to SAP B1. As a last step the invoice is created in R/3. Based on the configuration, the invoice triggers our fourth integration step. This step is converting the invoice in the B1 format, retrieves order information from SAP B1 to complete all information and hands over the invoice to SAP B1. This process will fail in case the human step (to mark the products as delivered) is not yet done. In this case the message will be handed over to the B1iSN Error Inbox. We configure an automatic action in B1iSN to retry the handover automatically in a certain time interval till the invoice is handed over successfully.
CitiXsys provides application integration services to large corporations with SAP ERP having subsidiaries, vendors and associated companies running SAP Business One.
Supply chain management applications (for managing inventory and shipping), customer relationship management applications (for managing current and potential customers), business intelligence applications (for finding patterns from existing data from operations), and other types of applications (for managing data such as human resources data, health care, internal communications, etc) typically cannot communicate with one another in order to share data or business rules. For this reason, such applications are sometimes referred to as islands of automation or information silos. This lack of communication leads to inefficiencies, wherein identical data are stored in multiple locations, or straightforward processes are unable to be automated.
Enterprise application integration (EAI) is the process of linking such applications within a single organization together in order to simplify and automate business processes to the greatest extent possible, while at the same time avoiding having to make sweeping changes to the existing applications or data structures. In the words of the Gartner Group, EAI is the “unrestricted sharing of data and business processes among any connected application or data sources in the enterprise.”
B1i Framework is the only integration framework with SAP Business One DI Adapter and integrates seamlessly SAP Business One with any application. CitiXsys is the leader of B1i integration services with largest number of B1i consultants globally engaged in several projects.