Non invoice related deductions through EDI

I am trying to automate the cash application process via the receipt of the customer inbound 820 (using message type REMADV, type PEXR2002). I can successfully post payment, clear open items, and set up deductions relating to a specific invoice, but I haven't been able to post deductions unrelated to an invoice. Our customers often take deductions not related to a specific invoice at the same time as remitting payment for invoices. Has anyone managed to post 'independent' deductions when posting a payment advice via EDI?

Hi Nile,
Am trying to understand the process around using EDI 820 for incoming payments and clearing customer accounts.
Would be great if you can share your expriences and also any documents that you might have.
Thanks,

Similar Messages

Invoice BLOCK & HOLD through EDI Processing

Hi SAP Gurus,
Can you please let me know as to how to BLOCK & HOLD Invoices while processing through EDI.
Regards,
Yasir

Hi ,
You can use the program RBDMANI2 which will reprocess all the IDOCs (EDIinvoices )that have failed . You can schedule this program in the background and it will post all failed invoices which have the GR posted later .
We had the same scenario and we have scheduled this program as a daily job at night .
Regards,
Hari.

Issue when the invoice is processed through Edi.

Hi Experts,
Purchase order reference line items are missing when the invoice is created using EDI.
Can any body have an idea on above given?
Regards,
SK.

Hi,
How you are creating invoice?
Creating based on data coming from Idoc or sending Invoice data as Idoc.
please elaborate.
Regards,
Bhavana.

Non PO Charges through EDI Incoming Invoice

Hi
I would be very thankful if somebody can answers these questions. I am designing EDI based invoice LIV.
1) Is it possible to post some charges in invoice which are without PO reference.Is it possible to post these kind of charges with EDI message INVOIC01 or we have to post through FI posting.? or we need to use INVOIC02
2) If possible through EDI in which segment of IDOC we will enter these charges with amt I am not able to find out the segment I tried in EIEDP01 but failed
3)Also is it possible to post credit memo also with EDI?
Thanks
[email protected]

try out with segment E1EDP05.

Urgent :Accounts Payabale Invoice automation through EDI

Hi All,
Through EDI, We would like to automate accounts Payable Invoice in SAP.
Kindly provide me the following details to create partner profile for this automation
1. Which Partner type ( Customer / Vendor / User / etc.,) to be used
2.Which Partner function to be used
3.Which Message type to be used
4. Which Process code to be used
Apart from the above process, any other settings are to be done for accounts Payable EDI automation.
Points will be rewarded.
Thanks & Regards,
A. Raja

Hi,
You can use invoic message type of IDOc for needed processing .& IDoc type will be either INVOIC01/INVOIC02.
Please provide additional details of trnasctions you would like to automate that will be helpful to provide further info.
Thanks.
Mark points if helpful.

Invoice through EDI

HI,
Can anybody let me know how the invoice(MIRO) get generated when vendor send an invoice through EDI. Is there any Job which creates the invoice using the IDOC.
Can anybody let me know the process flow and if possible transaction codes also.
Points will be awarded.
Regards,
Shree.j

Hi ,
Please refer the below link:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
http://help.sap.com/saphelp_erp2005vp/helpdata/en/2d/b12d3b1daca008e10000000a114084/frameset.htm
Please assign points as way to say thanks
Ravi

Sources of Invoices - Non PO related

Hi,
I have to separate PO related Invoices and Non PO related invoices by sources of invoices only.
Is there any table exist to find the sources of invoices.
Please help me regarding this.
Thanks in adv.
Eswar

Hi,
Go to MIR6 and enter the reference or any other criteria and execute,
Please reward if helpful,
Regards,
Chetan.

Purchase Order sending through EDI

Dear Experts,
I got a requirement recently for sending PO from SAP to vendor system (non SAP) through EDI interface.
Clients all purchasing and inventory is handling an out side vendor.
Anybody can help me with how SAP can link other system throuh EDI and make data transfers.
Thanks for your help
John K.

Hi,
As you are saying that the vendor is interested in reciving the PO through EDI, then you need to check all the below mentioned aspets when you are going to construct an interface:-
1. Which EDI message format (TRADACOM, ANSI or EDIFACT)
2. how are they going to receive it?
3. What fields needs to be mapped into the EDI message
4. Which version are they expecting.
5. What type of message are they expecting (like PO, GR or IR)
First check out on all the above questions, setting up an interface from SAP is easy the only thing which you need to do is going to on the EDI front.
I have used TLE, Harbinger, Gentran, XI and Pathfinder EDI sub systems to transmit the purchase and sales related information.
Thanks,
Mahesh.

Relation of ALE , EDI and idoc

HI
     what is relation of these ALE, EDI, IDOC , i know the definition of these , i want know ( while the transfer of sap to sap ALE tool is used ,) where this idoc is used ,
regards
shivaji

Hi Shivaji,
What is EDI?
Electronic Data Interchange
     The computer-to-computer electronic exchange of machine processable business documents in a standard format
     An electronic alternative to paper, fax, and phone-based transactions used by companies to communicate with one another
Purpose:
     Allows for better time management and relieves the entering of duplicate information while cutting down on discrepancies and human intervention.
     The Electronic Data Interchange component in Sales and Distribution consists of an Intermediate Document (IDoc) [Ext.] interface. You can use this interface to
     send messages (outbound processing) such as an order confirmation through Electronic Data Interchange (EDI)
     receive messages (inbound processing) such as a sales order through EDI
EDI:
     What?
     The technology of transmitting documents electronically
     Why?
     For Electronic Data Interchange between a company and trading partners
     How?
     By means of an electronic document - the IDoc
From the SAP side, the EDI interface is based on IDoc technology, which is independent of
EDI standards. All data is transferred in files between the R/3 System and the EDI subsystem.
Synchronous Remote Function Call (RFC) is implemented to define the time of transfer for a
file between the two systems. The following data can be transferred using the EDI interface:
Outbound Idocs: IDocs are transferred from the R/3 System to the EDI subsystem.
Inbound Idocs: IDocs are transferred from the EDI subsystem to the R/3 System.
Status report: The EDI subsystem sends a status report to the R/3 System on the progress of
the processing of the outbound Idoc.
Contents of IDOC
The data in every IDoc is exchanged between the SAP system and a subsystem in the following three record types, irrespective of the IDoc type:
     Control record (Table: EDIDC): Contains information about Sender and Receiver. There is only one control record per IDoc. It consists of
IDoc Number
Sender and Receiver information
IDoc Message Type* / Port.
IDoc Type / Direction / Current status / Partner No / Partner Type (Vendor/customer)
     Data record (Table: EDIDD): Contains the message to be exchanged between Sender and Receiver. An IDoc can contain multiple data records, as defined by the IDoc structure. Data records store application data such as purchase order / sales order header information, sales order details like sales doc #, Material / Qty and other relevant information.
     Status record (Table: EDIDS): Contains Status of IDoc at various stages, during the transmission of IDoc between Sender and Receiver. Multiple status records are usually attached to an IDoc. Status records are attached to an IDoc throughout the process like status code, date and time at every stage
Know Me
Basic Type: The form of IDOC type that is originally created in the system. Like ORDERS01 is a basic type IDOC for order messages. It is using the basic types only you would be able to enhance them to suit new requirements within the same IDOC structure. Any enhancement to the basic type IDOC will produce an Extension IDOC that would be more or less similar to the basic type with some new additions (of segments or fields). Here, I would go on to say that IDOC type and Basic type is the same thing that would be referred to interchangeably.
Message type: Again, obvious from the name, its the message that is being conveyed. A message type is assigned to the Basic type. Here, logical messages are assigned to the basic type to reflect a business message being transacted. For example, ORDERS is the message type for a purchase order sent by buyer to vendor. The use of which Basic type in this message will differ from buyer to vendor. Basic types used for ORDERS are ORDERS01/02/ etc...Also, one may come up with a custom built IDOC type (or basic type as you can say)...But it is essential to associate a message type with a basic type IDOC. This feature will enable the same IDOC type to be used for a related message. For example : ORDERS01 can be used for message ORDERS for posting a order, the same IDOC can be associated with message ORDCHG to indicate that the message is an order change and so the processing of this IDOC will change accordingly.
IDoc Type:
     Defines the structure of data records
      IDoc Type is used to understand the message in string form available in the data records.
      IDoc type is version dependent i.e an Idoc type can be used only in versions in and above the version in which IDoc is released.
      Transaction WE30 is used to define and release IDoc Types
      Newly created Idoc is a BASIC IDoc and modifications
             (Additions of segments) to IDoc after it has been released can be done by creation of extension      of IDoc.
      IDoc type can be defined by structuring Segments
Function Module: The most important player in the IDOC processing. This is nothing but an ABAP program to process the IDOC. SAP has supplied function modules to process all standard basic IDOCs and messages. A function module is determined based on the Basic IDOC type and the message type (also message code). So from the above descriptions about basic and message type, the combination of two would primarily determine which IDOC will process this idoc. As an instance, ORDERS01 with message ORDERS is configured to be processed by FM IDOC_INPUT_ORDERS. Similarly, ORDERS01 + ORDCHG will be processed by IDOC_INPUT_ORDCHG. Likewise, you can see all associations in WE57 for inbound. For out bounds, you would refer to process codes (WE41).
Segments: The idenfiers in the IDOC structure which indicates the data, their level, state of occurrence....You can take them as records in the IDOC. Each individual segment will come to you as a record in the IDOC. (Go to EDID4, provide an IDOC # and it will list all included segments as records.) Segments are logically nested to indicate various levels of data (header, item etc).
Qualifiers: Inside the segments, there are fields that can carry actual data often signified by use of qualifiers. A qualifier for a segment field would provide the exact meaning of the data. For example, E1EDK03 segment is configured for dates related data. Segment field IDDAT qualifies the date type and the DATUM field gives out the actual date. So you may see a date qualified as 002, which can be interpreted as requested delivery date. Likewise you can see all qualifiers and their meanings in the associated segment fields in SE12. Give the segment name and go to the domain the ranges for the ID fields.
How EDI Works
Sending Data
     Computer system serves as a data repository.
     EDI extracts information from existing computer applications.
     Transmits paperless, computer-readable documents via telephone lines.
Receiving Data
     Fed directly into a computer system.
     Automatically processed and interfaced with internal applications.
Processing Time
     Accomplished in minutes.
     No re-keying.
     No paper shuffling.
     No attendant costs of manual document processing and delivery.
What is the difference between ALE, EDI, IDocs and BAPI?
The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
ALE/EDI - Purpose
Electronic Data Interchange (EDI) and Application Link Enabling (ALE) are used for exchanging business data between different systems.
For both these forms of communication, you require the IDoc Interface. The IDoc interface is made up of the definition of a data structure and the processing logic of this data structure. The data structure is the IDoc. The IDoc is the general exchange format of the communicating systems. IDocs can be sent using different methods (for example, RFC or as a file).
Application Link Enabling (ALE)
You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems. ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
1.     ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor). The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12). This enables communication with non-SAP systems.
1.     By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message.
IDoc Interface/ALE
Purpose
The IDoc interface exchanges business data with an external system.
The IDoc interface consists of the definition of a data structure, along with processing logic for this data structure.
The data structure is the IDoc. The IDoc is the exchange format common to all the communicating systems. You can specify exception handling in the SAP Business Workflow, with IDocs, without the data already having to exist as SAP application documents.
You need the IDoc interface in the following scenarios:
Electronic data exchange (EDI)
Connect other business application systems (e.g. PC applications, external Workflow tools) by IDoc
Application Link Enabling (ALE).
Application Link Enabling (ALE) is a technology to create and run distributed applications
Hope this would help you.
Reward points if helpful.
Vamsi.

Create Purchase Order through EDI

Hello Everybody,
I want to know how to create Purchase order through EDI. I will receive text file from third party system. I have made most of the configuration related to EDI like Port -File, Partner Function etc. I am using message type PORDCR and Idoc type PORDCR05.
But i do not know how the SAP first will convert the text file into IDoc and then create Purchase order. Can any body help me how to go about it? What steps i have to follow. I will have text file from that i have to create Purchase order through EDI.
Thanks in advance.
Regards,
Manish

Hi,
Create Purchase Order through EDI
Regarding on your query,
You can use the standard ORDERS05 idoc type itself to send outbound idocs.
It will be the middleware or the integration team that will send this IDOC to the receiving system.
or
Maintain Partner Profile in WE20, RFC Connection to the Middleware in SM59 and Port in WE21.
Maintain Output Procedure/Output Type/Access Sequences/Condition Records from NACE
Generate the Outbound 850 (PO) from ME21N
Regards,
Sekhar

Posting Incoming payment through EDI 820

Hello,
I am trying to set up EDI 820. I want to post incoming payments through EDI 820.
IDOC Information
IDOC type: PEXR2002
Message type: REMADV
Function Module: IDOC_INPUT_REMADV
Process code: REMC
I have been testing using test tool all my idocs are failed. The error which I am getting is - "customer/vendor could not be determined for intermediate document".
Please suggest me how to fix this error. Is this related to FI config settings or ALE setting error.
Thanks & Regards,
Victor

Even i faced the same error while posting the EDI820. Then i corrected the errror by maintaining the segement E1EDKA1
Field name : PARVW , Value: AG
Field name : Name1, Value : Vendor number at customer location
And also the segment E1EDKA1
Field name : PARVW , Value: BE
Field name : Name1, Value : Vendor number at customer location
this should help you
IF E1EDPA1-PARTN IS INITIAL.
        IF E1EDPA1-NAME1 IS INITIAL.
*-- keine Daten uebermittelt => Fehler
          PERFORM STATUSFELDER_FUELLEN
                  USING FEHLER_BEI_UEBERGABE
                        MSG_WARNING
                        MESSAGE_ID
                        MUSS_FELD_FEHLT
                        'NAME1'
                        'E1EDPA1'
                        SY-REPID
                        'E1EDPA1_MOVES'
                        'NAME1'
                        SEGNUM
                        DOCNUM.
        ELSE.
          SCHLUESSEL = E1EDPA1-NAME1.
        ENDIF.
      ELSE.
        SCHLUESSEL = E1EDPA1-PARTN.
      ENDIF.
      IF NOT SCHLUESSEL IS INITIAL.
        PERFORM PARTNER_TABELLE_LESEN
                USING SCHLUESSEL PARTNERNUMMER
                      PARTNERART HILF_BUKRS.
You can also populate E1EDPA1-PARTN instead of NAME1 to find the account.

Purchase Order through EDI

Dear Experts,
I got a requirement recently for sending PO from SAP to vendor system (non SAP) through EDI interface.
Clients all purchasing and inventory is handling an out side vendor.
Anybody can help me with how SAP can link other system throuh EDI.
Thanks for your help
John K.

Hi,
You can use the standard ORDERS05 idoc type itself to send outbound idocs.
It will be the middleware or the integration team that will send this IDOC to the receiving system.
Regards,
Subramanian

Deduction through INF0045

Dear All,
I am facing one problem related to deduction through Infotype 0045.
Problem Detail -
In case of Full & Final (Recovery) processing system showing error with
a loan wage type 0045 (Message - A Loan Wage type in table RT should be
deducted, however the remaining net amount was too small wage
type /LEP, please lower the loan repayment in Infotype 0045, choose an
amount that can be duducted.)
Please suggest how we can recover complete balance Loan amount through
infotype 0045 which are more than earnings in case of Full & Final
(recovery) processing for a particular month.
Waiting for your reply.
Regards,
Gaurav Kumar
09911596677

Hi Mr. Das,
Thanx for your early reply.
We would like to make complete repayment through infotype 0045 in payroll run.
As per your suggestion we can do it by special repayment (externally) but we have requirement to deduct the same special repayment (internally).
Regards,
Gaurav Kumar
09911596677

Re : Inter company stock transfer through EDI

Hi
 How to do the intercompany stock transfer through EDI. In this if Purchase order is created from one comapny a sales order should created automaticall in another Company. Fot this what is the SPRO settings.
How to do this.
Thanks
Anto

Hi,
continues from here,
Inbound file: edi_in
Function module: See text below.
Status file parameters
Directory: /home/edi/<portname>/
Outbound file: status.idoc
Function module: Leave blank if using above
u2022 Both the portname and the exchange directory should be created according to the same naming convention. However, the portname should be in upper case whereas the corresponding directory name should be in lower case (see examples below).
 Portname (upper case):
 <portname>
 Exchange directory name (lower case):
 /home/edi/<portname>
 where <portname> consists of:
 EDI<system name><client number><id char>
 <system name> is the name of system on which port exists eg. F01, PG1 etc.;
 <client number> is name of client on system which will use this port; and
 <id char> is a single alphabetical character such as u2018au2019,u2019bu2019 etc. typically, u2018au2019 will denote dynamic outbound file naming (used for testing) whereas u2018bu2019 will denote static outbound file naming. All ports will use static inbound filenames.
For example, the name of a port using dynamic file naming on system F01, client 610 would be named EDIF01610A. The exchange directory would be named edif01610a. Similarly, the name of port using static file naming on system PG1, client 600 would be EDIPG1600B. The exchange directory name would be edipg1600b.
Note that the function u201CEDI_PATH_CREATE_USERNAME_DT_TMu201D can be used in the u201CFunction moduleu201D field of the Outbound file parameters if IDocs are to be written to multiple files. In this case, the corresponding outbound filename field should be left blank. The standard IDoc exchange interface between the SAP EDI component and the EDI subsystem uses a single file for each transfer direction. However, should the exchange interface change, or for testing purposes, the function modules for dynamic naming can be used.
2.4.2. Control of EDI processes in R/3
2.4.2.1. Maintain: Outbound Process Code (WE41)
IMGCross-Application ComponentsALE Extensions  Outbound
Check that the outbound EDI processes in the R/3 system are defined. Indicates which ABAP/4 function module to execute in order to create an outbound IDoc.
The following assignments are available for R/3:
2.4.2.2. Maintain: Inbound Process Code (WE42)
IMGCross-Application Components  ALE  Extensions  Inbound
Check that the inbound EDI processes in the R/3 system are defined. Indicates what kind of inbound processing to execute.
 A long list of options is available under Processing by function module, relevant ones are:
INVF INVOIC FI Invoice receipt (Financial Accounting)
INVM INVOIC MM Invoice verification (Mat Management)
ORDC ORDCHG Change customer order
ORDE ORDERS Create customer order
ORDR ORDRSP Purchase order confirmation
2.4.2.3. Control: System Process Codes (WE40)
 Choose Processing by task. Check that the codes indicating the type of EDI processing error are defined. The only valid entries are the entries shown on the screen, as they are directly called via the EDI basis module.
2.4.2.4. Control: Status maintenance (WE47)
 Check that the codes indicating status of IDoc processing are defined. The status values for outbound IDocs are between 01 and 39, while the status values for inbound IDocs begin with 50. These values are delivered by SAP and cannot be customised.
2.4.2.5. Control: Partner Types (WE44)
 Check that the codes that identify the commercial relationships between the receiver and sender are defined. Values are delivered by SAP. Names of the programs and routines that validates the entry of the EDI trading partner ID:
Partner type Report name Form routine
B - Bank RFETESTP READ_T012
KU - customer RSETESTP READ_KNA1
LI - vendors RSETESTP READ_LFA1
LS - logical system ( ALE) RSETESTP LOGSYS
2.4.2.6. Control: Forward Inbound (WE45)
Allows for the forwarding of IDocs to a specific application. Contains the exactly defined destination of an inbound IDoc within the SAP system. Usually no changes are required.
2.4.2.7. Control: Status Process code (WE56)
Choose Processing by task: The following set-up has been provided as default:
Process code: EDIS
Identification: TS30000078
Description: EDI-IDoc status record processing
The process code is for inbound status, The ID type is an identification code for inbound processing method (workflow or standard task) of the status record.
3. MM IMG CONFIGURATION
3.1. Global settings (IMG):
3.1.1. Units of measure (IMG  Global settings):
The ISO code is important for EDI. It is used to convert the internal SAP units of measure into standard units.
The MM configurer must link the Unit Of Measure, EACH, with the ISO code PCE (Piece).
3.2. Link Schema to Purchase order
Check the following:
IMG  MM  Purchasing  Message determination  Message determination  Message Schemas
Execute transaction u201CDefine Message Schemas for Purchase Orderu201D
Select transaction: Assign Schema to purchase order
Add: Usage =B for output
 Application = EF for purchase order
 Procedure = RMBEF1 for purchase order
3.3. Link application to EDI interface via message control:
IMG  MM  Purchasing  Messages  Output Control
Check following under Output Control:
 Condition table
 Access sequence
 Message types
 Message schema
 Output control
3.4. Enabling Multiple Output for Purchase Orders (Optional)
For example: EDI & Printing
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022 Create new access sequence (e.g. ZPUR), copy the access sequence 0001 but leaving the ''E'' flag blank (Exclusive is off). (Transaction M/50)
u2022 Goto Define message types  maintain message types:
 Create a new message type (e.g. NEU1), setting the output type to 1 for printed output and using ZPUR as access sequence. (Transaction M/34)
u2022 Goto Message Schema  define message schema  maintain output determination procedure:
 Update procedure RMBEF1 by adding a step for the new condition type (e.g. NEU1) prior to the standard delivered step for NEU. (Transaction M/36)
u2022 Goto Processing program  Define Processing program  Output program: Purchase Order.
 - Add a NEU1 record to table TNAPR. The program FORM Routine and layout must be specified. (Copy an existing NEU record). (Transaction OMTB)
u2022 Goto Processing program  Define Processing program  Output by partner type.
 - Add NEU1 record for VN (vendor). (Transaction OMTG)
3.5. Link Output type (fax=2, E-mail=7) to NEU (Purchasing)
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022 Goto Processing program  Define Processing program  Output program: Purchase Order.
 - Add another NEU record to table TNAPR with the appropriate output medium. Copy an existing NEU record. (Transaction OMTB)
u2022 Goto Processing program  Define Processing program  Output by partner type.
 - Add NEU record for VN (vendor). (Transaction OMTG)
4. SD APPLICATION REQUIREMENTS
Assumption: SD is only used for testing purposes and configuration is based on a need basis - only configure the minimum.
Reference SAP Course manual Chapter 11.
4.1. EDI Configurations
4.1.1. Conversion of SAP item categories to IDOC item categories (VOE1)
IMG  S&D  EDI  EDI Messages  Conversion of SAP item categories to IDOC item categories
Add the following entry:
For Standard Item description : 0 OR LDN
Typically error message: ''Transaction LDN is not defined".
4.1.2. Partner functions
IMG  S&D  EDI  EDI Messages  Configure EDI Partners Partner  Application  Partner function
Check that the following partner functions exist: (at least)
SP Sold-to party
VN Vendor
BP Bill-to party
SH Ship-to party
Note - the German abbreviation is passed to the IDoc.
4.2. S&D Sales Configurations
4.2.1. Maintain Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Define item categories
Add LDN for standard item:
 Item type = B
 Relev for billing = B
 Tick following: Bus data item
 Sched line allowed
 Credit active
 Pricing
 Screen seq. grp = N
4.2.2. Assign Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Assign item categories
Add/Update the following entries:
 1 2 3
Sales doc type OR OR OR
Item category group NORM DIEN LEIS
Item category LDN TAD
LDN LDN
4.2.3. Assign Schedule line categories
IMG  S&D  Sales  Sales document  Schedule lines  Assign Schedule line categories
Add Item category LDN to table (with no other parameters).
4.3. S&D Pricing Configurations
4.3.1. EDI pricing condition types
IMG  S&D  Basic functions  Pricing  Pricing control  Define condition types  Maintain condition types
Maintain the following condition types:
 EDI 1 - Calculate type =C for Quantity
 EDI 2 - Calculate type = B for Fixed amount
4.3.2. SD Pricing procedures (V/08)
IMG  S&D  Basic functions  Pricing  Pricing control  Define & Assign pricing procedures
Maintain pricing procedure for ZVAA01 (Standard).
Select control and add EDI1 and EDI2 as steps 1 and 5 respectively with no other parameters.
5. INVOICE IMG CONFIGURATION
No additional IMG configuration (not partner specific) was needed for Inbound Invoice processing.
Thanks,
Swamy H P

Scales when SO coming through EDI

As per the requirement, I have configured the settings related to Scale based pricing for a condition type in SD.
Since SOs are coming directly through EDI in the system, it is necessary to define a breakpoint in the EDI process: "that after reaching upto a certain quantity in the SO's first line item of a same customer, it should automatically enter the next quantity in the second line item of the same SO."
Then only the Scale rules would be applied correctly to the sales order.
EX: It is updating the quantity in the first line item of SO until the quantity reaches upto 1000 but from 1001 it should enter in the 2nd line item.
How would we configure the EDI process accordingly?
Thanks,
Juhi

Hi Juhi - At this moment, I wouldn't say that this is something possible through functional configuration. I've worked a lot with IDOCs and specially orders. This requirement of yours, splitting item lines based on the EDI line item quantity can be achieved through ABAP development at one stage in the IDOC posting function module.
IDOC_INPUT_ORDERS. This function module. after having interpreted the IDOC segments and various data requirements, builds BDC data for sales order creation before calling VA01. You can probably achieve your objective by writing in a code in the customer exit EXIT_SAPLVEDA_002 that it calls everytime it builds a BDC data (header, item etc)...you can do the following:
If OK Code is SICH, i.e the sales order BDC data has been realized, you can run through the BDC internal table records and identify line item data. If the quantity of the line item data is more than your single line limit, you can append the same records for the line item adjusting the quantities appropriately. I wish I could write in a code, but I am a functional person, so really wouldn't make sense writing in a ABAP that I don't know :).....but I think, this is what could help you in achieving the requirement. NOW, This you can limit to specific customer (again code the IF condition) or have this run for all customers. FLAW : Every order would be subjected to this process if you use it in general....
The other way would be to have this handled in your EDI sub-system. Where they would create E1EDP01 segment and its internal segments appropriately on encountering an item with more than 1000 quantity. Wouldn't that be great !!!! That would eliminate the SAP coding requirements.
Thanks
Nikhil

Non invoice related deductions through EDI

Similar Messages

Maybe you are looking for