EDI/ IDOCs - Invoice

Hi,
I have few questions regarding the inbound processof invoice:
1. What is the difference between 110 ( air freight details& invoice) and 820 ( billing) ?
2. I'm in 4.6C, For inbound 110 what is the IDoc type/ Process Code and Message Types to be used?
- INVOIC01 for IDOC type is this correct? and Process Control is it INVL or INVM?
3. Steps to configure - transactions/ details?
Thanks in advance.
Renu

Hi
110 and 810 are different types of invoices based on their functionality with different doc type
you can use the same Basic Idoc type message type for the,
see the EDMSG for message types and
EDBAS for Idoc Types and take the correct one and use
Data Creation in Idoc
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.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
Create Message Type (WE81)
Create Segment type (WE31)
Create IDOC Type (WE30)
Assign Segment type to Idoc Type (WE30)
Assign Idoc Type to Message Type (WE82)
Assign Function Module – Mtype – Idoc Type (WE57)
Create a Process Code – (WE41-outbound, WE42-Inbound)
Enable Customized FM to ALE (BD51)
Assign these to Partner Profile (WE20)
check the following thread:
/message/2222912#2222912 [original link is broken]
http://help.sap.com/saphelp_erp2005vp/helpdata/en/e6/04c03e7856b300e10000000a114084/frameset.htm
<REMOVED BY MODERATOR>
Regards
Anji
Edited by: Alvaro Tejada Galindo on Apr 29, 2008 3:30 PM

Similar Messages

  • EDI - Incoming Invoice Error and GR based Invoice Verification - 51 No GR

    Hi,
    We are implementing EDI for incoming invoices and use Goods Receipts based Invoice Verification.  When processing an inbound IDOC Invoice (type INVOIC01) where the Goods Receipt has not yet been posted, then Inbound IDOC is siiting at Error Status, 51 - No GR documents found.
    Is there any way we can process this as a Parked Invoice or for Verification in the background (MIRA)?  because the current situation is a problem, as 95% of our Inbound Invoices will be received electronically before the Goods are Received. 
    The actual Vendor's delivery note is stored in the segment E1EDP02 (Qualifier 016), field BELNR.
    Currently the IDOC as to sit in error until the Vendor's Delivery Note is Goods Receipted which can be several days later - SAP OSS Note 393883 fro 2001 suggests doing this, but surely this is a common situation.  The IDOC sitting in error in WE02 in the list of IDOCs is difficult to isolate from true errors.
    If this is was mnaul Invoice it could be processed through MIRA for background Invoice Verification later with program RMBABG00.
    We havd SAP version ECC 6.0
    I have spotted OSS Note 501524 which implies that is possible automatically Park Incoming EDI IDOC Invoices, has anyone tried this?  and what would be the transaction/program that could be used to post several at once when the GR has been processed (similar to RMBABG00)

    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.

  • IDOC Invoices and EDI Invoices

    Hi Gurus,
    Please help me in understanding the flow of IDOC Invoices and EDI Invoices.
    What is the purpose of using IDOC and EDI? How it works?
    Please revert asap.
    Thank You

    HI Verma,
    You can post the invoices in SAP system through IDOCs.
    Mostly, this activity is performed/triggered, when the invoice data is with third party.
    Third party will have the invoice data base and sends a file to SAP.
    SAP XI will map/convert the file(sent by third party) to fields in SAP and posting of invoice happens.
    Please refer the below links for EDI Invoices
    EDI invoices
    Creating EDI Invoices
    Hope this will help you in understanding IDOC invoices and EDI Invoices.
    Regards,
    Praisty
    Edited by: Praisty on Dec 22, 2009 1:20 PM

  • Processing options for EDI vendor Invoices

    I'm trying to get a better understanding of what my options are for processing EDI vendor invoices and would appreciate some help.  I'm using  message type INVOIC02 with process code INVL and in configuration I've set the processing option in table T076S to 4 (tolerence corresponding to online processing).  When an invoice fails either the vendor specific tolerance check or the payment blocking checks the invoice gets parked with error status 3.  This is behaving as I would expect.  The issue I have is the price on the parked invoice is the price from the PO and not the price from the EDI segment.  Is there anyway to change this?  This makes it difficult to analyze the cause of the error without going back to the Idoc segments.  I've tried playing with the other processing options but they also enter the PO price in the parked invoice.  If it's not possible to change this are there any tricks that i'm missing that can help the users analyze the cause of the errors without going back into the idoc?
    thanks,

    If anyone has any expierence with this, I would appreciate any advice you may have.
    thanks,

  • EDI IDOC generation for interface with Vendor software help needed.

    EDI IDOC help needed.
    We are NOT an EDI shop, but have a project to output data to Sales Force.com
    Sales Force requests IDOC output - eg. 810 Outbound Invoice.
    We will need to do a historical load of Orders/Quotes/Invoices from the past 2 years.
    Is there a function module or series of FM's that are used to generate the E2EDKxxxxx type segments?
    I have been testing using the IDOC_OUTPUT_INVOIC and IDOC_OUTPUT_ORDRSP FM's, but they generate segments begining with E1EDKxxxxx.
    Basicall we have a report program that the user enteres in the date range of Order/Quotes/Invoices they wish to extract, the the program needs to output a flat file (.txt) on the server which is then picked up by Sales Force.com.
    Also, is there a way to have in the Partner Profile a generic Partner under the "Type KU" that can be used for all orders/invoices so I don't have to create a KU Partner Type for each and every Sold-To customer we have?
    I am very new to EDI so any help would be greatly appreciated.
    Thanks.
    Scott.

    Hi Scott,
    We will need to do a historical load of Orders/Quotes/Invoices from the past 2 years.
    I know it's very tempting to use an interface for such loads if you anyhow have to create one. However, often the volume alone speaks against interface usage for such scenarios.
    Is there a function module or series of FM's that are used to generate the E2EDKxxxxx type segments? I have been testing using the IDOC_OUTPUT_INVOIC and IDOC_OUTPUT_ORDRSP FM's, but they generate segments begining with E1EDKxxxxx.
    Well, the E2* segments basically reflect the external name of the IDoc segment, whereas the function modules you're referring to basically just create an internal version of the IDoc. Once the IDoc framework then passes the IDocs to the partner, the segment names usually (depends on how the IDocs are passed on) get converted to their external name. If there are multiple versions of a segment, then the version number will be appended to the segment name.
    Note that IDoc segment definitions are only partially stored in the data dictionary. If you want to see all versions you should always use transaction WE31 to look at segments. There you can also see for example for E1EDK01 the several versions and when you then use in SE37 function module SEGMENT_EXTERNAL_NAME_GET you will see what SAP produces as the external name for segment E1EDK01. This function module is basically the one that handles the segment name translations.
    Ignore the comments for subsystem, this is basically an option in SAP to possibly trigger further external tools (e.g. mapping etc.) for handling the outbound IDocs.
    Again, the funny thing is that via the WE30 transaction, if i put in INVOIC02 as the Obj. name and see the segments, i can see that E2EDK01 there is a version 005, but if i go to SE11 and put in E2EDK01005 structure line and i get a "not found". We just have up to E2EDK01002.
    In the old days SAP used to generate E1, E2 and E3* structures in the data dictionary (SE11). The E1* structure reflected the character type representation of an IDoc segment, whereas the other two (definition and documentation) contained actual references to data elements (e.g. if you used a quantity field). However, in newer releases those dictionary structures (E2* & E3*) are no longer generated, because they're superfluous (meta data defined via WE31 is sufficient).
    Cheers, harald

  • EDI vendor invoice and account invoice

    can u please explain me
    1.EDI Vendor Invoice
    2.Account Invoice

    EDI Vendor invoice is nothing but the LIV or FB60 invoice posted using EDI that is IDocs...
    and account invoice u can say FB60 invoices, that is they are posted only in accounting. they do not have a purchase order or a gr..
    Regards
    Anantha

  • 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.

  • EDI/ IDOC

    Gurus
    Can somebody answer my querries
    1. What exactly is gapping and mapping in EDI/IDOC
    2. Can anybody send me the functional specifications and test development  for EDI! Meaning any specs as a functional consultant we provide EDI team for mapping .
    My email ID is [email protected]
    Thanks

    Dear Brendon,
    what you map in IDOC depends on the IDOC message type.
    ORDERS - creation of a sales order
    ORDCHG - change of an existing sales order
    ORDRSP - confirmation/replication of the sales order
    DELINS - creation of a delivery schedule in scheduling agreement
    DELORD - creation of a delivery order to the scheduling agreement
    EDLNOT - creation of an external agent delivery to the scheduling agreement
    GSVERF - creation of a credit advice
    SBINV - creation of the invoice
    SBWAP - creation of debit/credit memo(requests)
    INVOIC - sending the invoice
    In the transaction WE60 you can see the fields to every basic IDOC type. Not all fields which could be mapped via IDOC will be transfered automatically (only some ones). All other fields can be mapped to the application with the help of numerous user-exits provided.
    The most important transactions:
    BD87 - to apply the incoming IDOC
    WE19 - to copy / to edit the IDOC and apply this copy
    WE02 - to display the IDOC
    WE05 - to select IDOCs
    WE60 - to see the declared IDOC fields
    And here is a general information about IDOC concept in SD:
    The EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.
    If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every thime send a change to the existiong order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).
    So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, INVOIC.
    That's all concerning the SD-EDI.
    Additional processes in SD, where EDI are used:
    1) application of delivery schedules to the scheduling agreement: IDOC of type DELINS
    2) creation of a delivery order to the scheduling agreement: IDOC of type DELORD
    3) creation of external agent service delivery to scheduling agreement: IDOC of type EDLNOT
    4) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV.
    It is all processes which are realized in the SD module via EDI.
    There is not so much Customizing for EDI. The most entries are required by EDI for the scheduling agreement processing (DELINS, EDLNOT, SBINV). The Customizing of these processes is located in the Customizing of scheduling agreements: SPRO => Sales and Distribution => Sales => Sales Documents => Scheduling agreements with delivery schedules => Control EDI Inbound processing.
    General EDI Customizing in SD is available under: SPRO => Sales and Distribution => Electronic Data Interchange => EDI messages => ...
    I hope this info helps.
    Kind regards,
    Akmal Vakhidov
    Development Support SAP, Walldorf/Germany

  • EDI incoming invoice error M8 755 Enter a tax code in item...

    All,
    Can anyone tell me where I should look to resolve this issue?  I'm trying to post an EDI incoming invoice for a PO.   The PO has an tax code on the line item being invoiced.  
    Thanks
    Sandra

    Let me get into a little more detail.  We have EDI incoming invoices working properly in our production environment.  It is unlikely our mapping or our customization is incorrect.   It is possible that something has been changed with customization but I have already looked there and did not see anything of concern.    
    I'm doing testing in our test environment using WE19, and I'm getting this error message although the idoc I create is similar to examples in production and the PO is also similar to what is in production. 
    I was hoping that someone had experienced a similar issue and would be able to point me in a direction that I have not already looked.
    Regards,
    Sandra

  • EDI/IDocs for WMS

    Hi all,
    I need sample code and processing steps for EDI-IDocs for WMS concept.

    Hi,
    check this it wil be helpful to you.
    Electronic Data Interchange
    Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
    Refer
    http://www.erpgenie.com/sapedi/index.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
    https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
    http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
    http://www.erpgenie.com/sapedi/index.htm
    http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
    EDI FLOW :
    Here is some thing which helps you and here the purchase order is taken as example too..
    Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
    What parts of the business cycle can be supported by EDI?
    Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
    How does EDI get started?
    EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
    What is the flow of EDI?
    The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
    check this.
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
    https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
    http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
    http://www.erpgenie.com/sapedi/index.htm
    http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
    cheers,
    sowjanya.

  • TAX ASSESSMENT BASIS MISSING IN SEGMENT E1EDK04 FOR IDOC INVOIC

    Hello,
    Tax assesment basis is missing in segment E1EDK04 for IDOC INVOIC. In EDI messages,Tax assesment basis has to be sent in TAX segment together with VAT rate. When there is only one VAT rate this is not a problem as tax assessment basis is the total net amount (And we have it in the IDOC). On the other hand when there is more than one VAT rate in the invoice, we don't have in the IDOC the Tax assesment basis of each VAT rate.
    Did someone experience this issue ? How did you handle it ?
    Regards.
    Eric.

    Dear Eric
    The latest pack available now for these components are (for PI 7.1)
    SAP BASIS 7.11 support package 6
    SAP HR 6.04 with Support Package 44
    If you are in PI 7.0 then I suggest you download the latest patch from marketplace.
    Sourabh

  • Best practise for EDI-IDOC scenario

    I want to create a EDI-IDOC scenario for invoicing our customers.
    There are 2 options that I can use, create partner profiles of type KU for each of our customer that we will be invoicing or have
    a LS for XI and configure the same.
    My company has around 400 customers. So incase i chose to go with KU then i have to configure 400 partner profiles right?
    Which is the best practice for this scenario?

    As stated above, you can use LS partner instead of KU partner. There are, however, some pros and cons to be considered:
    1) Post-processing agent assignment. If you have different people working with different customers you can assign them as post-processing agents to the respective partner profiles. If you switch to LS you will need to have only one agent (it might be a group of people though).
    2) When you have a separate profile for each customer then the customer number is included in the IDoc control record. This allows to quickly view the IDocs by customer number. E.g. if a customer calls and asks where the heck is my document then customer service could easily see all the IDocs for that customer in WE05, for example, and check what's going on. With LS they would have to dig into the segments for that.
    So the business process requirement decides this. If you don't care for any of this you might be even better off using LS instead of KU, because it requires less maintenance.

  • IDOC Invoices

    Hi Gurus,
    Please give me some information related to IDoc Invoices.
    What is IDoc invoices and what is the use of it?
    How can we implement it?
    Please revert asap.
    Thank You
    Regards

    HI,
    see customizing: Financial Accounting -> Acc. receivable and acc. payable -> business transactions -> incoming invoices / credit memos -> EDI and if you want to post intercompany invoices via IDOC Sales and Distribution -> Billing -> Intercomp. billing -> Automatic posting to vendor account (EDI). Read the documentation for this customizing node and the points below. See SAPNET for Details (308989,...)
    Next time pls. make a forum search before you post your question.
    BR Christian

  • Interface between sap to non sap using edi idoc

    hello abaper's,
                         i have requirment on creating Interface program for downloading files(PO)  from Non-sap system  to sap system using EDI Idoc techniques.pls give me a good tips for this requirment..
    With Regards
    MurugeshRajeev

    Hello,
            First of all, we'll need to identify as to what we want to do with the PO Data. For example, If we want to Create Sales Order, there is already a Posting Program available with the Name IDOC_INPUT_ORDERS (FM). This is useful for Creating a Sales Order automatically whenever a PO IDoc is received.
    Here is the Information for processing Standard IDoc.
    1. WE30 - ORDERS05 - IDoc  Type
    2. WE31 - Segment Definition for the IDoc Type
    3. WE81 - Logical Message Types (ORDERS)
    4. WE82 - Assigning the Message Type to IDoc Type
    5. WE42 - Define Process Code
    6. BD51 - If you want to Code a Custom Function Module,
                  then after creating it, you need to register the same
                  Function Module in this Transaction Code.
    7. WE57 - Assign Message Type / IDoc Type / FM group.
    8. WE20 - Partner Profiles
    9. WE21 - Port Definitions
    Hope this information was helpful.
    Thanks and Regards,
    Venkat Phani Prasad Konduri

  • SAP R/3 Mapping with EDI IDOC's 846 and 852 (Outbound)

    Hi:
    How are the following EDI IDOC Types mapped in SAP - R/3?
    1. Inventory Inquiry / Advice (846)
    2. Product Activity Data (852)
    What is the basic type, message type, idoc type that has to be used
    in both the cases - outbound based ones.
    This is a consumer products industry and not a retail industry. This
    is a hypothetical scenario where the end customer would like to see
    the price and the stock from all the plants and then place an order
    (846); and also see what is being planned in aparticaular plant for
    a planning period (852). The cycle countings are carried out based
    on the type of product in question and SAP-R/3 has been set up for
    this. What is the trigger point for the enitre activitiy to take
    place. Any valuable suggestions or guidelines are most welcome.
    Regards
    Rohit

    Check this link and see if it leads you somewhere.
    http://sap.ittoolbox.com/groups/technical-functional/sap-interfaces/information-on-the-edi-idoc-types-1739410
    http://www.jt77.com/CRM/related-discussion-1111.html
    Regards,
    Ravi Kanth Talagana

Maybe you are looking for

  • Enhance SRM-SUS

    I trying enhance srmsus application. First, copy SRMSUS to ZSRMSUS by BSP_CUSTOMIZE. Next create new Zview in ZSRMSUS and new Zcontroller. Next enter new line in table BBPC_SUS_ACTION with ID: ZZNEW NAME: 'ZZ' controller_name: Zcontroller controller_

  • Delivery date determination in the schedule lines

    Hi,        I have a question on the delivery date determination in the schedule lines of the sales order. If the goods issue date in the schedule line has been determined as 17th Aug 2009, and the transit time is 3 days. What should be the delivery d

  • Getting 'No Data found' Error when clicking the edit link to edit a record.

    Application Express 4.2.0 Database: oracle 11g Hi Guys I am getting an error whenever i try to edit some of my entries by clicking the edit link, i have a composite Primary key attributes of three columns ( Budget Year ('YYYY'), Training Name('VARCHA

  • Is it possible to remote-access my MacBook Pro away from home?

    Is it possible to remote-access my MacBook Pro away from home? What I currently have: Late-2011 MacBook Pro 8,2 (OSX Mavericks 10.9.5) 2.5ghz Intel i7 quad-core 16gb RAM, 1024gb SSD raid-0 (internal) Connecting to the internet through: Apple Time Cap

  • Time capsule channel settings

    Hello, I moved from Taiwan to the EU and need to adjust the channels of my Time Capsule 5GHz WLAN to comply with the EU standard? How can select the different channels. I currently have only 4 channels 149 - 161 available. I have tried to select the