Posts

SAP Press Books Sample Chapter Collections – Part 3

If you are new to this series, click to see all parts created under SAP Press Sample Chapter Downloads. Here is the third part of series you will find useful information about

  • Enterprise SOA definition and Enterprise Data Management’s role in it
  • An extended overview of SAP ERP HCM Components
  • Specs and business processes for 850-Interface ORDERS interface within EDI
  • An Overview of Procurement in Logistics
  • Special features of SAP APO and Advantages of planning with APO-PP/DS.
  • Introduction to SAP Upgrade Tools

Read more

Inter Company Billing Tutorial: Automatic Posting To Vendor Account

Automatic posting to vendor account is done by EDI. In our case where both companies are proccessed in the same system (& client), it is sufficient to create Idoc.

This document covers following steps for this process

  1. Creating a Customer to represent the receiving Company.
  2. Creating a Vendor to represent the supplying company.
  3. Creating a Port
  4. Maintain an Output Type
  5. Creating a Logical Address
  6. Creating a Partner Profile for both Customer & Vendor
  7. The relevant MM customizing is maintained.
  8. The relevant FI customizing is maintained.

Read more

Benefits of the EDI Processes

EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network. EDI is also called paperless exchange.

Implementing EDI benefits both the sender and the receiver. It is a mutual effort, and its benefits are maximized by sharing information in a timely manner. The benefits include

  • Reduced data entry errors. EDI does not involve data entry at multiple points. In the traditional process, a sender creates a purchase order on the system, prints the order, and then faxes or mails it to
    a trading partner. The receiver then rekeys the same information on his or her computer. The process is prone to data entry errors. This procedure is repeated when invoicing takes place. With EDI, data goes directly from one computer to another without involving a human being.
  • Read more

    Interface Detailed Design

    The purpose of this document is to outline the technical design of the EDI interface from SAP to the EDI subsystem. The high-level details of the proposed solution may be found in the EDI Scope document, as well as the EDI Functional Specification document. Further information on the interface may be obtained by reading the EDI Production Setup Guide. Read more

    Overview of EDI and IDoc Interface

    The purpose of this document is to provide a high-level overview of how EDI works in SAP and to introduce some fundamental concepts about IDocs. The information presented should be used during the interface technical design process. Read more

    Handling Inbound EDI Transactions

    Electronic Data Interchange (EDI) is about doing business and carrying out transactions with your trading partners electronically. On SAP side, EDI is handled through IDocs. When the data comes into SAP, it is called inbound transaction. When the data goes out of SAP, it is called outbound transaction. This presentations provide detail about some common inbound EDI scenarios that are handled in SAP with the examples and solutions.

    Contents:

    What is Inbound EDI?
    Example of an Inbound EDI data
    Inbound EDI explained
    Example of an Inbound EDI data how it looks after it came into SAP
    Transactions that are used in SAP to view inbound EDI data
    Finally how it looks after posting to an application
    Read more

    Commonly used EDI signals

    EDI 850(Purchase Order)
    An EDI 850 Purchase Order is an electronic version of a paper Purchase Order.A buyer will use the 850 Purchase Order to communicate to a supplier the specific items, price, and quantities they wish to have delivered.Each EDI Purchase Order document will have data organized into segments and data elements.Each segment contains at least one data element. Each data element is a data field. Examples of data elements on the Purchase Order include vendor number, item, quantity, price per item, street address, city, state and zip code, just like on a paper purchase order. The standards bodies have allowed for every conceivable possibility for data on the EDI Purchase Order document. Any one company will use a small subset of the available choices within the ANS X.12 or UN/EDIFACT standards Read more