CN102098287A - Method for realizing data transmission between system applications and products in data processing (SAP) system and business to business (B2B) system - Google Patents
Method for realizing data transmission between system applications and products in data processing (SAP) system and business to business (B2B) system Download PDFInfo
- Publication number
- CN102098287A CN102098287A CN2010105934298A CN201010593429A CN102098287A CN 102098287 A CN102098287 A CN 102098287A CN 2010105934298 A CN2010105934298 A CN 2010105934298A CN 201010593429 A CN201010593429 A CN 201010593429A CN 102098287 A CN102098287 A CN 102098287A
- Authority
- CN
- China
- Prior art keywords
- data
- sap
- transmission
- information
- edi
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The invention provides a method for realizing data transmission between a system applications and products in data processing (SAP) system and a business to business (B2B) system, which is characterized by comprising the following steps: establishing an interlayer of an electronic data interchange (EDI) server, and then sending data to be transmitted and a transmission request to the EDI server by the SAP system; applying queue treatment to carry out information transmission by the EDI server, and updating data in each server in a distributed architecture as well as ensuring the transmission safety by password authentication; carrying out information interaction in the B2B system; and passing back confirmed or returned information to the SAP system by the EDI server. In the method, a queue is adopted in the EDI server, thus solving the problems of the timely transmission and exact update of the information; by using the password authentication, the problem of the transmission safety is solved; the EDI server is used as the interlayer to connect the SAP system with the B2B system, thus avoiding pairwise mutual connection between different SAP systems and B2B systems, thus simplifying the integration difficulty among the systems, reducing the cost, realizing the distributed architecture, and being beneficial to upgrading or updating the systems.
Description
Technical field
The present invention relates to the electronic data interchange in the computer communication network, relate in particular to the method for SAP system and B2B inter-system data transmission.
Background technology
Electronic data interchange, being EDI (Electronic Data Interchange), is according to agreement, the economic information with certain architectural feature, by the electronic data communication network, between commerce and trade partner's computer system, exchange automatically and handle automatically.The EDI standard mainly contains U.S. ANSI X.12 series standard, Europe " commercial data exchange (TDI) " standard, and UNECE's electronic data interchange standard (EDI FACT) etc.These standards have comprised various information code required in the trade; Message, data element, complex data unit, data segment, grammer etc. have been comprised; Applying flexible can also be expanded according to own needs; Be applicable to all kinds of computers and communication network.
Businessman (general reference enterprise) is to the ecommerce of businessman, i.e. B2B (Business to Business).Be meant that the both sides of supply and demand of carrying out e-commerce transaction all are businessman's (or enterprise, company), they have used technology or the various commerce NET platform of Internet, finish the process of business transaction.These processes comprise: the issue supply-demand information, and to order goods and confirm and order goods, signing and issuing, transmit and receiving of payment process and bill determined distribution project and monitored delivery process etc.
SAP (systems applications and products in data processing) is a software that is used for the Enterprise Resources Plan management, and SAP carries out the EDI transmission by the ALE/IDocs interface mechanism based on the EDI standard.ALE/IDocs be SAP company for the interface mechanism that SAP R/3 R4.6C version is provided, be most widely used at present.This scheme has realized distributed framework.Because the restriction of server performance and region, a common company can after still separating, just have several, tens server application distribution on many machines.Different machines is being stored relevant master data, and the data in changing will make the data on other servers also will do corresponding change, and this has suitable workload and risk.And introduced ALE/IDocs, and as long as there is a machine to change, will initiate a message from other associated servers of trend, can accomplish that distributed data revises automatically.This is necessary for trans-regional large-scale company.
ALE (Application Link and Enabling) is that SAP carries out the designed integration middleware of transfer of data between SAP and non-SAP system and each SAP system, is specially adapted to the exchanges data between large enterprise's built-in system.IDoc (Intermediate Document) is data or the information format that SAP provides system integration special use.It almost can transmit any SAP application data.IDoc comprises 3 types: controlling recording, data record and state recording based on text character.Controlling recording mainly is a text message, as IDoc type, transmission/recipient's information and textual mark; Data record is management and real data part, and state recording is used for following the trail of the state of a text delivery point, as conditional code, system time, error identification etc.
For realizing transfer of data between SAP and the B2B system, originally all be to adopt the mode of mail or FTP to transmit to realize, be that the data that SAP will transmit generate the IDoc formatted file, send to the B2B system by mail or FTP then, the B2B system upgrades and maintenance information data after the information of receiving.
But there are some defectives in the transmission means of existing mail or FTP.(1) in the system of distributed structure/architecture, adopt the implementation efficient of mail transmission lower, can't reach the purpose that related data information is transmitted timely and effectively, upgraded, and mail loses easily, risk is bigger; (2) mode that adopts FTP to carry out transfer of data and share though can upgrade and maintenance information data, can't be controlled operating right, also can't in time accomplish the mutual response between system.
Summary of the invention
The present invention proposes the method for a kind of SAP of realization and the transmission of B2B inter-system data, main reference of the present invention the EDI framework of SAP, when realizing the transfer of data of SAP and B2B system, set up EDI server intermediate layer, the utilization formation solves the timely transmission and the problem of accurately upgrading of information in the EDI server; By password authentication, solved assurance safety of transmission problem; Connect SAP system and B2B system by the EDI server as the intermediate layer, avoided the interconnection in twos of different SAP systems and B2B system, simplified the integrated difficulty between system, reduced integrated cost.
System architecture of the present invention as shown in Figure 1, B2B system 2 and SAP system 1 link by EDI server 3, transmit data queue 4 between any two, client 5 links to each other with B2B system 2 respectively with supplier 6; And realize that according to following steps SAP and B2B system data transmit (as Fig. 2):
The 1st step: data that the SAP system will transmit (as: relevant informations such as order, buying) and transmission request send to the EDI server;
The 2nd step: the EDI server is after the information of receiving, and the utilization queue processing is carried out message transmission in the EDI server, and Data Update in each server in the distributed structure/architecture, guarantees safety of transmission by password authentication, transmits in the B2B system then;
The 3rd step: carry out follow-up processing (such as carrying out data interaction etc. with client or supplier) in the B2B system, operation acknowledgement is carried out to the information that receives in the back of finishing dealing with, and notice EDI server process finishes;
The 4th step: the EDI server returns the system to SAP to the information of confirming or return.
Realize method of the present invention, compared with prior art, beneficial effect mainly is the following aspects:
At first, compare with traditional Email, by EDI server queue transmission data, significantly reduced transfer of data chance of makeing mistakes and the time of waiting for data transmission and processing by this programme, make system transmissions reach the state of automation, promoted the promptness and the accuracy of transmission.
Secondly, compare with FTP, the latter lacks enough security controls, also can't satisfy the demand of synchronous immediate updating.And transmit by the present invention, the EDI server provides different passwords for each SAP system and B2B system, can only grab each autocorrelative data in transmission course, guarantees safety of data transmission; In the SAP system, there is data transmission request to output in the EDI server queue, just trigger data transmission immediately of data is found in the formation of EDI server detecting real-time.
At last, this scheme has realized distributed structure/architecture, more helps the upgrading or the update of system.The reception of data, transmission, transmission all are to be undertaken by the EDI server in this scheme, this has also shielded the difference of each system, as long as guaranteeing the data format unanimity just can, therefore the user only need revise or redesign separately that the relative program of system gets final product when system upgrade, and need not the concern of data transmission problem.
Description of drawings
With embodiment the present invention is described in further detail with reference to the accompanying drawings below.
Fig. 1 is B2B system and SAP system transmissions framework
Fig. 2 is B2B system and SAP data transmission procedure
Fig. 3 is to be example with the shipping message transmission, its B2B system data processing procedure.Wherein,
The 1:SAP system
The 2:B2B system
The 3:EDI server
4: data queue
5: the client
6: supplier
Embodiment
The invention will be further described below in conjunction with drawings and Examples.
System architecture of the present invention as shown in Figure 1, B2B system 2 and SAP system 1 link by EDI server 3, transmit data queue 4 between any two, client 5 links to each other with B2B system 2 respectively with supplier 6.
Transmitting step of the present invention as shown in Figure 2.The EDI server is receiving the sale (Sales) that the SAP system is imported into, order (PO), shipping relevant informations such as (Shipping), then being transferred to the B2B system handles, after finishing dealing with, B2B system feedback operation result information, and by the EDI server information of confirming or return is passed back to the SAP system once more.Realize the method for SAP and B2B system data transmission, the transfer of data between the system adopts the file format of XML, and concrete steps are as follows:
The 1st step: SAP converts related data to the IDoc file earlier, convert EDI standard XML file format to by higher level service application programming language ABAP program then, data in the XML file have comprised the relevant information that will transmit, secondly also show the IDoc number, make things convenient for tracking mode or error of transmission, then the content in the XML file is write additional (Add-On) and show in addition maintenance and management, notify EDI server reception data at last; The 2nd step: the EDI server carries out Authority Verification earlier to receiving data queue, reading of data again after checking is passed through, and transmit queue is put in the request will transmit, is undertaken according to priority the XML file transfer that generates in the add list to the B2B system by the backstage service then; The 3rd step: the B2B system carries out data interaction with client or supplier again after receiving data, usually adopt EDI or the Rosettanet agreement that meets the relevant standard of industry during data interaction, at last the information of returning is transferred back to the EDI server with the XML file format.The 4th step: after the EDI server receives the information of being returned by the B2B system, and confirmation feeds back to the SAP system the most at last.
Below be the concrete implementation process of example explanation with the transfer of data of Shipping.At first the data transaction that delivery is relevant in the SAP system is become the IDOC file, convert the XML file format of EDI reference format then to by the ABAP program, give the B2B system by the EDI Server Transport then, the B2B system will carry out respective handling again and will be transferred to the client after will receiving data, after transmission is finished successful information be fed back to the EDI server and will return the system to SAP by the EDI server.Its concrete process is as follows:
In the SAP system, create the Shipping request, trigger EDI output back and generate the IDoc file by business applications interface BAPI.IDoc information is recorded in three tables: (1) " EDIDC " controlling recording information, the direction that has write down IDoc is " ORDERS ", transmit leg and recipient and numbering for departures, IDoc type for sale, type of message.(2) " EDIDD " data record information has write down all transmission information of Shipping, as customer information, customer order information, product information, batch, batch quantity quantity, invoice information etc.(3) " EDIDS " state recording information, the whether success of generation state, database change daily record and the handler and the time etc. of having write down IDoc.
Then generate the XML file by the ABAP program.Secondly the relevant information that not only comprises Shipping in the XML file also shows the IDoc number among the XML, makes things convenient for tracking mode or error of transmission.After the XML file generates, write in the Add-on table in addition maintenance and management.Then send the transmission request to the EDI server, the information that comprises transmission and password in the transmission request, the EDI server at first carries out purview certification after receiving information, verification by after will transmit request and put into transmit queue, undertaken giving the B2B system with the XML file transfer that generates in the Add-on table by the backstage service then according to priority.
The B2B system triggers transfer process after receiving information, as shown in Figure 3, generate the Shipping file and be transferred to the client according to the customer requirement form, the Shipping file format is shown in the following inventory, after transmission is finished successful information is fed back to the EDI server, last EDI server is put into information notification queue and is given the SAP system by backstage service passback.
With the shipping message transmission is example, and its B2B system data transformat inventory is as follows:
-<ShipmentNotificationReport>
-<Header>
+<Sender>
+<Receivers>
+<DocumentDefinition>
</Header>
<NrShipmentNotifications>1</NrShipmentNotifications>
-<ShipmentNotification>
<STShipmentNumber>SFKC7PO552</STShipmentNumber>
<ShipmentDATeTime>20100411T060000.000Z</ShipmentDateTime>
<InvoiceNumber>UNKNOWN</InvoiceNumber>
+<ShipFrom>
+<ShipTo>
<NumberOfShippingContainer>1</NumberOfShippingContainer>
-<ShippingContainer>
<STParcelNumber>SFKC7P055201</STParcelNumber>
+<MassDimension>
+<Quantities>
-<ShippingContainerItem>
<STBulkId>FOK160010001</STBulkId>
-<Quantities>
<QtyType>Packaged</QtyType>
<UnitCode>Wafer</UnitCode>
<Qty>23</Qty>
</Quaantities>
-<Lot>
<SubconLotId>EA1031.1</SubconLotId>
<LotType>P</LotType>
-<Quantities>
<QtyType>Ship</QtyType>
<UnitCode>Wafer</Unitcode>
<Qty>23</Qty>
</Quantities>
-<ProductInfo>
<ProductCode>C9799A02</ProductCode>
<ProductType>Wafer</ProductType>
<PartID>RC3436_A</PartID>
-<Quantities>
<QtyType>lnvoiced</QtyType>
<UnitCode>Wafer</UnitCode>
<Qty>23</Qty>
</Quantities>
-<DocumentReference>
<DocumentLabel>Purchase?Order</DocumentLabel>
<DocumentId>XT4501114132</DocumentId>
</DocumentReference>
</ProductInfo>
</Lot>
</ShippingContainerItem>
-<ShippingContainerItem>
...
Claims (10)
1. the method for SAP system and B2B system data transmission, B2B system and SAP system link by the EDI server, it is characterized in that, realize that according to following steps SAP and B2B system data transmit:
The 1st step: data that the SAP system will transmit and transmission request send to the EDI server;
The 2nd step: the EDI server is after the information of receiving, and the utilization queue processing is carried out in message transmission and the distributed structure/architecture Data Update in each server in the EDI server, guarantees safety of transmission by password authentication, transmits in the B2B system then;
The 3rd step: carry out data interaction in the B2B system, operation acknowledgement is carried out to the information that receives in the back of finishing dealing with, and notice EDI server process finishes;
The 4th step: the EDI server returns the system to SAP to the information of confirming or return.
2. according to the method for claim 1 described SAP system and the transmission of B2B system data, it is characterized in that: the EDI server provides different passwords for each SAP system with the B2B system.
3. according to the method for claim 1 described SAP system and B2B system data transmission, it is characterized in that: B2B system and SAP system only link by the EDI server, and the reception of SAP system and B2B inter-system data, transmission, transmission all are to be undertaken by the EDI server.
4. according to the method for claim 1 described SAP system and the transmission of B2B system data, it is characterized in that: the transfer of data between the system adopts the file format of XML.
5. according to the method for claim 1 described SAP system and B2B system data transmission, it is characterized in that: in described the 1st step, the SAP system sends to the data of transmission and transmission request before the EDI server, SAP converts related data to the IDoc file earlier, convert EDI standard XML file format to by higher level service application programming language ABAP program then, data in the XML file have comprised the relevant information that will transmit, then the content in the XML file are write additional (Add-On) table.
6. according to the method for claim 5 described SAP system and the transmission of B2B system data, it is characterized in that: also show the IDoc number in the described XML file.
7. according to the method for claim 5 described SAP system and B2B system data transmission, it is characterized in that: IDoc information is recorded in three tables: (1) controlling recording information comprises direction, IDoc type, type of message, transmit leg and recipient and the numbering of IDoc; (2) data record information comprises customer information, customer order information, product information, batch, batch quantity quantity, invoice information; (3) state recording information, the generation state, the database that comprise IDoc are changed daily record and handler and time.
8. according to the method for claim 5 described SAP system and the transmission of B2B system data, it is characterized in that: SAP generates the IDoc file by business applications interface BAPI.
9. according to the method for claim 1 described SAP system and B2B system data transmission, it is characterized in that, described the 2nd step handles in the following sequence: the EDI server carries out Authority Verification earlier to receiving data queue, reading of data again after checking is passed through, transmit queue is put in the request will transmitted, and is undertaken giving the B2B system according to priority with the XML file transfer that generates in the add list by the backstage service then.
10. according to the method for claim 1 described SAP system and B2B system data transmission, it is characterized in that: adopt EDI or the Rosettanet agreement that meets the relevant standard of industry in described the 3rd step during data interaction.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010105934298A CN102098287A (en) | 2010-12-17 | 2010-12-17 | Method for realizing data transmission between system applications and products in data processing (SAP) system and business to business (B2B) system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010105934298A CN102098287A (en) | 2010-12-17 | 2010-12-17 | Method for realizing data transmission between system applications and products in data processing (SAP) system and business to business (B2B) system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102098287A true CN102098287A (en) | 2011-06-15 |
Family
ID=44131150
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010105934298A Pending CN102098287A (en) | 2010-12-17 | 2010-12-17 | Method for realizing data transmission between system applications and products in data processing (SAP) system and business to business (B2B) system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102098287A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103744991A (en) * | 2014-01-21 | 2014-04-23 | 国家电网公司 | Method for XML-based data transmission between SAP systems |
| CN103793808A (en) * | 2013-12-31 | 2014-05-14 | 青岛中科软件股份有限公司 | SAPBONE management system |
| CN103870532A (en) * | 2012-12-12 | 2014-06-18 | Sap股份公司 | Advanced Business Query Language |
| CN105005837A (en) * | 2014-04-21 | 2015-10-28 | 山西太钢不锈钢股份有限公司 | Method for adding approval function to SAP ERP application program |
| CN105550912A (en) * | 2015-12-21 | 2016-05-04 | 浪潮软件集团有限公司 | SAP platform-based electronic invoice processing method and device |
| CN112838935A (en) * | 2019-11-22 | 2021-05-25 | 北京沃东天骏信息技术有限公司 | Electronic data exchange method and system |
| CN113283639A (en) * | 2021-04-25 | 2021-08-20 | 唐山钢铁集团有限责任公司 | SAP system and energy system data transmission method |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1525366A (en) * | 2003-03-01 | 2004-09-01 | 鸿富锦精密工业（深圳）有限公司 | Periodic audit report system and method |
| US20060106755A1 (en) * | 2004-11-12 | 2006-05-18 | Sap Aktiengesellschaft, A Germany Corporation | Tracking usage of data elements in electronic business communications |
-
2010
- 2010-12-17 CN CN2010105934298A patent/CN102098287A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1525366A (en) * | 2003-03-01 | 2004-09-01 | 鸿富锦精密工业（深圳）有限公司 | Periodic audit report system and method |
| US20060106755A1 (en) * | 2004-11-12 | 2006-05-18 | Sap Aktiengesellschaft, A Germany Corporation | Tracking usage of data elements in electronic business communications |
Non-Patent Citations (1)
| Title |
|---|
| 于渌: "基于SAP R/3系统的EDI标准报文格式转换及发送", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103870532A (en) * | 2012-12-12 | 2014-06-18 | Sap股份公司 | Advanced Business Query Language |
| CN103870532B (en) * | 2012-12-12 | 2019-04-05 | Sap欧洲公司 | Higher level service query language |
| CN103793808A (en) * | 2013-12-31 | 2014-05-14 | 青岛中科软件股份有限公司 | SAPBONE management system |
| CN103744991A (en) * | 2014-01-21 | 2014-04-23 | 国家电网公司 | Method for XML-based data transmission between SAP systems |
| CN103744991B (en) * | 2014-01-21 | 2017-07-07 | 国家电网公司 | A kind of method of data transfer between SAP system based on XML |
| CN105005837A (en) * | 2014-04-21 | 2015-10-28 | 山西太钢不锈钢股份有限公司 | Method for adding approval function to SAP ERP application program |
| CN105550912A (en) * | 2015-12-21 | 2016-05-04 | 浪潮软件集团有限公司 | SAP platform-based electronic invoice processing method and device |
| CN112838935A (en) * | 2019-11-22 | 2021-05-25 | 北京沃东天骏信息技术有限公司 | Electronic data exchange method and system |
| CN113283639A (en) * | 2021-04-25 | 2021-08-20 | 唐山钢铁集团有限责任公司 | SAP system and energy system data transmission method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102098287A (en) | Method for realizing data transmission between system applications and products in data processing (SAP) system and business to business (B2B) system | |
| US7236947B2 (en) | Providing highly automated procurement services | |
| US7945498B2 (en) | Method for facilitating chemical supplier transactions | |
| US8386332B2 (en) | Community management for electronic peer to peer business to business transactions | |
| CN1388933A (en) | Method and apparatus for communicating order entries in a network environment | |
| GB2378544A (en) | Online purchase of shipping and insurance services | |
| CN104574010A (en) | Customs warehousing and customs affair management system as well as customs warehousing and customs affair management method | |
| US20020069121A1 (en) | Supply assurance | |
| CN109102345A (en) | A kind of different purchase orders intersection tune pallet piling up method and system of B2B E-commerce | |
| Dale | The management of engineering change procedure | |
| JP4212785B2 (en) | Settlement mediation system and settlement mediation method | |
| US20020091590A1 (en) | Fundraising system with creation, coordination, and order tracking tools | |
| US20050080644A1 (en) | Self-describing business document collaboration protocols | |
| KR101429115B1 (en) | Integration Material-Distribution System for Identifying | |
| CN106991530A (en) | E-commerce platform, financial managing and control system, economic law business application system and SAP system integrated interface data transmission method | |
| US20020174039A1 (en) | Virtual hub | |
| EP1342184B1 (en) | Method and system for enhancing a commercial transaction conducted via a communications network | |
| CN113822633B (en) | Consignment system management system and method thereof | |
| CN1393782A (en) | Virtual inventory center system | |
| CN114119092A (en) | Management method and system for echelon battery supply chain | |
| US20200387855A1 (en) | Sales management system and sales management method | |
| Hayashi et al. | Document exchange model for augmenting added value of B2B collaboration | |
| KR20080097255A (en) | Business to business integration | |
| KR20220049635A (en) | Logistics Brokerage System Using the Web Page of the Internet | |
| CN114240286A (en) | Inventory business data processing method, system, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20110615 |