Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 235 views

    Template O810v4010 Sample

    Uploaded by

    simhan_1983
    This document provides a sample mapping of data elements between an X12 810 invoice transaction and an IDoc for sending invoices from SAP to a trading partner. It includes the segment, data element, SAP IDoc field, qualifier field and any notes for each element. Maintaining customer and partner master data, configuring outbound parameters and output types, and developing conversion rules for fields like SCAC and BOL number are identified as key considerations for implementing this invoice mapping.

    Copyright:

    © All Rights Reserved
    Download as XLS, PDF, TXT or read online from Scribd

    Template O810v4010 Sample

    Uploaded by

    simhan_1983
    235 views8 pages
    This document provides a sample mapping of data elements between an X12 810 invoice transaction and an IDoc for sending invoices from SAP to a trading partner. It includes the segment, data element, SAP IDoc field, qualifier field and any notes for each element. Maintaining customer and partner master data, configuring outbound parameters and output types, and developing conversion rules for fields like SCAC and BOL number are identified as key considerations for implementing this invoice mapping.

    Original Description:

    Template o810v4010 Sample

    Original Title

    Template o810v4010 Sample

    Copyright

    © © All Rights Reserved

    Available Formats

    XLS, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides a sample mapping of data elements between an X12 810 invoice transaction and an IDoc for sending invoices from SAP to a trading partner. It includes the segment, data element, SAP IDoc field, qualifier field and any notes for each element. Maintaining customer and partner master data, configuring outbound parameters and output types, and developing conversion rules for fields like SCAC and BOL number are identified as key considerations for implementing this invoice mapping.

    Copyright:

    © All Rights Reserved
    Download as XLS, PDF, TXT or read online from Scribd
    Download as xls, pdf, or txt
    235 views8 pages

    Template O810v4010 Sample

    Uploaded by

    simhan_1983
    This document provides a sample mapping of data elements between an X12 810 invoice transaction and an IDoc for sending invoices from SAP to a trading partner. It includes the segment, data element, SAP IDoc field, qualifier field and any notes for each element. Maintaining customer and partner master data, configuring outbound parameters and output types, and developing conversion rules for fields like SCAC and BOL number are identified as key considerations for implementing this invoice mapping.

    Copyright:

    © All Rights Reserved
    Download as XLS, PDF, TXT or read online from Scribd
    Download as xls, pdf, or txt
    of 8
    At a glance
    Powered by AI
    The document provides details on mapping fields from an SAP idoc to an X12 810 invoice document.

    The document provides details and comments on mapping segments from an SAP idoc to an X12 810 invoice document.

    The document lists various segment codes (ISA, GS, ST, BIG, etc.) that are mapped in the 810 document.

    250630150.xls.

    ms_office

    Sample 810 mapping document


    X12 Transaction
    X12 Version
    Idoc Type
    Message Type
    Direction to SAP
    Created by
    System ID
    Sender Port
    Logical System
    Client
    Partner Number
    Remit To
    Order Type
    Sales Org
    Dist Channel
    Division
    Unit of Measure
    Language
    Currency
    Sender ID
    Sender ID Qual
    Receiver ID
    Receiver ID Qual
    GS02
    GS03

    The Wella Corporation Confidential

    810
    4010
    INVOIC01
    INVOIC
    Outbound
    Kevin Wilson
    SAPDEV
    SAPEDI
    LOGSYS005
    005
    10000111
    Sample Company Name
    OR
    0010
    10
    10
    EA
    E
    USD
    <senderid>
    01
    <receiverid>
    08
    <sendergs>
    <receivergs>

    11/9/2014

    Page 1

    Sample 810 mapping document


    Segment
    ISA01
    ISA02
    ISA03
    ISA04
    ISA05
    ISA06
    ISA07
    ISA08
    ISA09
    ISA10
    ISA11
    ISA12
    ISA13
    ISA14
    ISA15
    ISA16

    Data Element Name


    Authorization Information Qualifier
    Authorization information
    Security information Qualifier
    Security information
    Interchange ID Qualifier
    Interchange Sender ID
    Interchange ID Qualifier
    Intechange Receiver ID
    Interchange Date
    Interchange Time
    Interchange Standards Identifier
    Interchange version ID
    Interchange Control Number
    Acknowledgement Requested
    Test Indicator
    Component Element Separator

    GS - Functional Group Header


    GS01
    Functional ID
    GS02
    Application Senders Code
    GS03
    Application Receiver's Code
    GS04
    Date
    GS05
    Time
    GS06
    Group Control Number
    GS07
    Responsible agency code
    GS08
    Version
    ST -Transaction Header
    ST01
    Transaction Set ID
    ST02
    Transaction Set Control Number
    BIG - Beginning Segment (MANDATORY)
    BIG01
    Date
    BIG02
    Invoice Number
    BIG04
    Purchase order Number
    REF - Reference Identifier (PD)
    REF01
    Reference Identification Qualifier
    REF02
    Reference Identification

    Codes and comments


    "00" No Authorization information
    Ten Blank Positions
    "00" No Security Information
    Ten Blank Positions
    01
    <senderid>
    08
    <receiverid>

    Field

    Qualifier Field

    E1EDK03
    E1EDK01
    E1EDK02

    DATUM
    BELNR
    BELNR

    IDDAT

    "012"

    QUALF

    "001"

    E1EDKT2

    TDLINE

    TDID

    ZE1T

    Qualif: "PD:"

    E1EDKT2

    TDLINE

    TDID

    ZE1T

    Qualif: "IA:".

    :
    00403
    0
    P
    >

    "IN" Invoice
    <sendergs>
    <receivergs>

    X
    004030

    "810"

    Invoice Date

    CCYYMMDD

    Promotional deal number

    REF - Reference Identifier (IA) (MANDATORY)


    REF01
    Reference Identification Qualifier
    REF02
    Reference Identification

    "IA" Internal Vendor Number


    "123456789"

    N1 - Name (BY) (MANDATORY)


    N101
    Entity Identifier Code
    N103
    Identification Code Qualifier

    "BY" Buying Party


    "92"

    810 Mapping Template

    Qualifier Value Notes on Mapping Document

    Idoc Segment

    250630150.xls.ms_office

    Page 2

    Sample 810 mapping document


    Segment

    N104

    Data Element Name

    Codes and comments

    Identification Code

    Idoc Segment

    Field

    E1EDKA1

    KNREF

    Qualifier Field

    PARVW

    Qualifier Value Notes on Mapping Document

    WE

    4 Digit location or consolidated SCAC


    entered in Partner Description field on
    the Partners tab of the customer master.
    No ST segment is sent because Maisto
    receive no orders that have a separate
    ST segment that differs from the BY
    segment in the 850

    ITD - Terms of Sale (MANDATORY)


    ITD01
    Terms Type Code
    ITD02
    Terms Basic Date Code
    ITD07
    Terms net Days

    "01"
    "2"
    Net Days

    E1EDK18

    TAGE

    QUALF

    "001"

    DTM -- DATE/Time Reference (MANDATORY)


    DTM01
    Date/Time Qualifier
    DTM02
    Date

    "011" Shipped
    Date Shipped

    E1EDK03

    DATUM

    IDDAT

    "001"

    Date Shipped

    IT1 - Baseline of Item Data (MANDATORY)


    IT102
    Quantity Invoiced
    IT103
    Unit of Measure code
    IT104
    Unit price
    IT106
    Product/Service ID Qualifier

    "EA"
    Price per U of M
    "CB" Buyers catlaog number

    E1EDP01
    E1EDP01
    E1EDP26

    MENGE
    MENEE
    BETRG

    QUALF

    "001"

    Must invoice in eaches


    Must use decimal point

    IT107
    IT108

    Product/Service ID
    Product/Service ID Qualifier

    Buyers number
    "UP" UPC Customer Package Code

    E1EDPT2

    TDLINE

    TDLINE

    "CB:"

    E1EDPT1 = Z2ET. In E1EDP19


    segment as well

    IT109

    Product/Service ID

    UPC Number

    E1EDPT2

    TDLINE

    TDLINE

    "UP:"

    E1EDPT1 = Z2ET. In E1EDP19


    segment as well

    PID - Product / Item Description


    PID01
    Item Description Type

    "F" Free Form


    E1EDP19

    KTEXT

    QUALF

    "002"

    E1EDPT2

    TDLINE

    TDLINE

    "PACK:"

    PID05

    Description

    PO4 -- Packing Information (MANDATORY)


    PO401
    Pack

    Basic
    Delivery Date

    TDS - Total Monetary Amount (MANDATORY)

    TDS01

    Amount

    CAD - Carrier Detail (MANDATORY)


    CAD01
    Mode
    CAD04
    SCAC
    CAD05
    Routing
    CAD07
    Carrier Reference Number Quailifier

    810 Mapping Template

    E1EDS01

    SUMME

    SUMID

    "011"

    E1EDKA1
    E1EDKA1

    LIFNR
    NAME1

    PARVW
    PARVW

    "SP"
    "SP"

    Formatting: Two decimal places are


    assumed. Example 1526 will be
    interpreted as 15.26.

    "M" Motor (Common Carrier)


    Carrier's Name
    "CN"

    250630150.xls.ms_office

    Page 3

    Sample 810 mapping document


    Segment

    CAD08

    Data Element Name

    Codes and comments

    Reference Number

    Idoc Segment

    E1EDK01

    Field

    Qualifier Field

    Qualifier Value Notes on Mapping Document


    From conversion rule BOLNR. The BOL
    number must be entered in the delivery
    header field LIKP-BOLNR located on the
    Delivery Header - Transport Rel. Info
    screen - Bill of Lading number

    AUGRU_BEZ

    SAC -- Allowances and Charges


    SAC01
    Allowance or Charge Indicator

    This value will be defined by the specific


    allowance or charge value that is
    presented in the E1EDS01-SUMIDF field

    SAC02
    SAC05

    "A" Allowance
    C310 or H000
    Service, Promotion, Allowance, or Charge Code
    Amount

    SAC12

    "02"
    Allowance or Charge Method of Handling Code

    E1EDS01

    I410
    A Conversion must often be performed
    in order to take the SAP R/3 value and
    convert it into the predefined EDI
    allowance or charge code.
    E1EDS01

    ISS -- Invoice Shipment Sumary (MANDATORY)


    ISS01
    Number of Units Shipped
    ISS02
    Unit of Measure
    ISS03
    Weight
    ISS04
    Unit of Measure
    CTT -- Transaction Totals (MANDATORY)
    CTT01
    Number of Line Items

    810 Mapping Template

    SUMID

    SUMME

    Calculated by the translator

    Sum IT102
    IT103
    E1EDK01
    E1EDK01

    BRGEW
    GEWEI

    E1EDS01

    SUMME

    250630150.xls.ms_office

    Convert LBR to LB

    SUMID

    "001"

    Can be calculated

    Page 4

    Action
    Maintain the customer master data for the bill-to:
    Enter sold-to customer number.
    Click on [Sales area data].
    1. On the Sales view, enter the Acct. at Cust. (KNVV-EIKTO) - This value must match what the customer sends
    on the order in the REF02 with qualifier IA
    2. On the Partners view you need to enter the SCAC code for each of the applicable ship to parties in the Partner
    Description field. Also applicable for the carrier detail if it is implemented this way.
    Create a partner profile for the bill-to partner (BP):
    Partner type: KU
    Make an Outbound parmtrs. record for Message type 'INVOIC' 1. Outbound Options Receiver Port: EDIPORT
    Syntax check: x
    Basic type: INVOIC01
    Transfer Immediately: x
    2. Message Control Application: V3
    Message type: Z810
    Process Code: SD09
    3. EDI standard EDI Standard: X
    Message type: 810
    Version: 004010
    Configure an output type for EDI invoices. This output type was configured as Z810
    VOE4 must be populated with the ship to entries as well as the applicable carrier entries
    VK11 needs to maintained for PR00 standard pricing
    VD52 - Material determination needs to be configured to cross reference the customers material numbers to ours
    XD02 - Change the vendor (Carriers) to include the relevant SCAC code in the SCAC field
    BD55 - Assign rule SCAC and BOLNR to customer 100376

    Considerations

    Need user specs for whether both printed and EDI output should be proposed, or whether they are exclusive.
    Any restrictions?

    The SCAC rule: Puts the SCAC code in E1EDKA1-LIFNR for PARVW = SP
    The BOLNR rule: Puts the BOL number (LIKP-BOLNR) in the E1EDK01-AUGRU_BEZ field

    Orders

    Date

    Invoice

    Date

    Name

    03/27/03 Kevin Wilson

    Version

    Nature of Change
    1 Created document

    You might also like