Send Wire information to Bank through EDI

Hello All,
I am trying to generate a file that will be send to the disbursement bank to wire money to our suppliers. This file will be generated by Payment batch and send to the back via EDI.
Can we use standard EDI outbound process to format this payments.
Any help will be appreciated.
Thank you
Ashish

Please clarify what search has been done before posting the question.
If you know the EDI transmission number then simply typing in Google 'EDI <#> IDoc' finds all the information needed.

Similar Messages

  • Check Payment advice through EDI

    Hi,
    I need a solution to send the payment advice to bank through EDI.
    For that i created partner profiles for vendor and bank. I activated EDI in vendor master also.
    And i attached EDI accompaying sheet also to the FBZP t code.
    for this we created a new payment method and testing. it is working.
    our client is asking: He want to send the payment advice for the payment method 'C' - Check to his bank through EDI. What we have to do for this.
    For this if we give C in payment method in F110 we have to use payment method program only not EDI program.
    Please guide me
    sateesh kumar

    Hi Sateesh,
    Generally payment advices are directly sent to Vendor, but sometimes clients will sent the payment details and payment advice to the bank.
    In your case, if u want to select the Payment Method C, then if u give RFFOEDI1 program for EDI setting, then u cant print your cheques locally.
    One Alternative is that use Payment Medium Workbench (PMW) in that check management option is present, try with that.
    I am not sure how far it is going to be successful.
    Regards
    srikanth

  • Goods Supplier details through EDI - Purchase Order

    Hi All,
    We are sending purchase orders to vendor through EDI. Generally we do not have details of the Partner - Goods Supplier (GS) in the idoc in the segment E1EDKA1. .
    Now our client wants to show the details of GS also in the segment of the idoc. As per SAP note 456127 , SAP has not given provision for it.
    Has anyone got this type of requirement , and has someone any idea on adding a new segment showing Goods Supplier in it.
    Thanks in advance.
    Regards,
    Vengal Rao.

    Hi,
    Please check the below links...
    http://help.sap.com/saphelp_sm40/helpdata/en/af/5f28a7669648dfb71b418d243f2a82/content.htm
    http://help.sap.com/saphelp_sm32/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/content.htm
    Hope it may helps you.
    Kuber

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

  • How to Send Purchase Order through EDI/IDOC.

    Hi Experts,
    We are using SAP ECC.5. And intending to send the Purchase Order to Supplier through EDI/IDOC and Receive the Inbound Acknowledgement.
    Appreciate, if you could help me, the required Configuration details for outbound and inbound (PO & Acknowledgement).
    Reg
    Kumar

    Hi Kiran
    Many thanks for the response. It is true that by changing the message type to EDI can generate idoc. What is not clear is any other config we need to do interms of Message generation, Resubmitting failed IDOC etc..
    Out requirement is that we would generate the IDOC for New and changed docs and send to external EDI converter.
    Inbound, receive the IDoc and post the acknowledgement.
    Appreciate, if you could forward any document link which can explain the details.
    Reg
    Kumar

  • ALE Error while sending PO IDOC through EDI

    Hi Experts,
                      I am sending one PO IDOC through EDI but I am getting the following error:-
                      Message no. B1130.
                      "Too many recipients found for message type ORDERS in the ALE model"
                      How can I solve this error ? Please guide me in this regards as this is an
                      important issue with urgency.
    Thanks & Regards
    Jitendra Gujarathi

    Please check this discussion thread
    Re: Too many recipients found for message type in the ALE model

  • Inbound Interface for Accepting Bank Statement Through EDI

    Hi All ,
                    Pls Help me out to complete this  Scenerio with u r Ideas and Inputs .
        Inbound Interface for Accepting Bank Statement Through EDI.
    Rgds
    Rafi .

    Hi,
    INBOUND:
    Step 1. EDI Subsystem creates an IDoc file from EDI Messages
    2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
    3. Data in Control Record is validate against the Partner Profile.
    4. IDoc is generated in Database and syntax check is carried out.
    5. IDoc file is deleted once file read.
    6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
    7. Check for Process Immediately.
    If NO
    Execute RBDAPP01 Program
    Else
    Read Process Code from Partner Profile
    Process Code Points to Function Module
    Application Document Posted.
    further help:
    check url
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training

  • PO Revisions through EDI

    Hi All,
    We used to send POs to some other Application through EDI. One of the POs has not interfaced to the third party Application through EDI. We have checked all the trading partner and supplier setups. The only issue we have found is that the PO has been revised as it has Printed_Date and print_count is present in PO_HEADERS_ALL.
    So pls suggest how can we push PO revisions through EDI.
    Version - 11.5.10.2
    Thanks!!!!

    Hi,
    If you wish to receive vendor confirmations via EDI, the IDoc interface must have been installed
    When an order acknowledgment is received via EDI, the system checks whether just the acknowledgment number is to be recorded, or also quantities and dates.
    Refer the attached link for more information on customization settings;
    http://help.sap.com/saphelp_46c/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
    If you work exclusively with order acknowledgments, only the acknowledgment number is recorded on the item detail screen. (In this case, no confirmation control key exists.)
    If you work with several confirmation categories and therefore a confirmation control key exists in the PO or scheduling agreement item, the quantities and dates shown in the order acknowledgment are recorded by the system.
    If you want to take a look at acknowledgments that have been received, choose Item ® Confirmations ® Overview from the item overview. Column C (creation indicator) contains the value 3, meaning that the acknowledgment was received via EDI.
    Br,
    Tushar

  • Remittance Advice to Vendor through EDI, message REMADV

    Hi Guru
    I want to send a remittance advice to vendor only through EDI after running payment run. But standard SAP requires configuration for Vendor and as well as House Bank and generates two Idocs one for bank(Message type PAYEXT-PEXR2002) and one for Vendor(Message type REMADV-PEXR2002).
    The requirement is only to send the remittance advice to vendor but not to the bank is any way that i can stop generating idoc to bank.
    THANKS & REGARDS
    Pavan
    Edited by: Pavanks on Sep 14, 2009 10:28 AM
    Edited by: Pavanks on Sep 14, 2009 10:29 AM

    hi Pavan,
    you want to do the open item clearing without the banking file throught auto payment run, do you? can you try to use other payment method , like check.
    thansk

  • Payment information to vendor through E-mail

    Presenetly using SAP ver 4.7. How to automate this procedure that as soon as a payment is made, an email is generated and sent to vendor.
    thanks
    anu

    Hello Anu, take a print out and go through the below documentation. Hope it helps.
    Suresh
    Process Flow for ERS
    Use
    Created goods movements can be settled without receipt of an invoice. The system can create and post the appropriate invoices itself. This makes transmitting an invoice from vendor to customer and the consequent invoice verification unnecessary. You can send the information contained in settlement documents to the vendor as printed documents, by fax, EDI, or the Internet.
    Prerequisites
    Master data
    You have created a material with a Purchasing view, or you are settling purchase orders with account assignments.
    The purchase order price for the materials ordered must not be an estimated price.
    In the vendor master, you have flagged the GR-based Inv. ver. and Auto GR Setmt fields.
    Movement data
    You have created a MM scheduling agreement or purchase order. If you select the GR-based Inv. ver. and Auto GR Setmt fields in the vendor master, the system automatically selects them as a default in the purchasing document. At least one schedule line exists for your scheduling agreement.
    A tax code must be maintained in the scheduling agreement or purchase order.
    The goods receipt must refer to a purchase order or scheduling agreement.
    To send settlement documents to the vendor, make the settings for message determination.
    You can deselect the GR-based Inv. ver. field in the purchase order item if required. For single purchase orders you can also deselect ERS in the purchase order item, or exclude them from ERS in the info record of the material.
    Process Flow for ERS
    Use
    Created goods movements can be settled without receipt of an invoice. The system can create and post the appropriate invoices itself. This makes transmitting an invoice from vendor to customer and the consequent invoice verification unnecessary. You can send the information contained in settlement documents to the vendor as printed documents, by fax, EDI, or the Internet.
    Prerequisites
    Master data
    You have created a material with a Purchasing view, or you are settling purchase orders with account assignments.
    The purchase order price for the materials ordered must not be an estimated price.
    In the vendor master, you have flagged the GR-based Inv. ver. and Auto GR Setmt fields.
    Movement data
    You have created a MM scheduling agreement or purchase order. If you select the GR-based Inv. ver. and Auto GR Setmt fields in the vendor master, the system automatically selects them as a default in the purchasing document. At least one schedule line exists for your scheduling agreement.
    A tax code must be maintained in the scheduling agreement or purchase order.
    The goods receipt must refer to a purchase order or scheduling agreement.
    To send settlement documents to the vendor, make the settings for message determination.
    You can deselect the GR-based Inv. ver. field in the purchase order item if required. For single purchase orders you can also deselect ERS in the purchase order item, or exclude them from ERS in the info record of the material.
    Messages
    Use
    You can create messages when posting an invoice in ERS. You can send messages externally to vendors by printout, fax, EDI, and email. This includes PDF documents. The messages can be sent as follows:
    explicitly, using the function Output messages
    immediately on posting the invoice or credit memo
    in the background, at a time specified by you
    You define corresponding jobs for the program MM70AMRA. If you start one of these jobs, all messages that correspond to the selection criteria are outputted.
    If you do not want to generate any messages, select the field No message creation on the selection screen. Your messages are not transmitted to the vendor.
    Prerequisites
    Maintain the EDI partner profiles using the SAP Easy Access Menu : Tools ® Business Communication ® IDoc Basis ® IDoc ® Partner Profile. For more information on maintaining EDI partner profiles, see in the SAP Library Basis Services / Communications Interface (BC-SRV) ® The IDoc Interface (BC-SRV-EDI) ® IDoc Interface / Electronic Data Interchange (BC-SRV-EDI) ® Defining Partners.
    Function
    Settings in the IMG for Logistics Invoice Verification:
    Define the messages that are to be created when an invoice is posted.
    Message Determination ® Maintain Message Types
    Define the text modules that the form should contain.
    Message Determination ® Define Forms
    Message Determination ® Define Sender Details for Forms
    Define the time and medium to be used to send the messages.
    Message Determination ® Maintain Conditions
    Maintain the EDI partner profiles.
    EDI ® Enter Program Parameters.
    Features
    Define text modules for form
    You save standard texts per company code, which are then outputted at fixed points in the form MR_PRINT by the print module. The form MR_PRINT is used by the ERS settlement document. The following text modules are processed:
    Text type
    Position
    Example
    Header text
    top right of the form
    Logo
    Footer text
    on every page of the form as footer text
    Information on the company
    Sender
    above the address
    Sender of company code
    If you work with various languages, you must create the texts in all of the languages.
    Activities
    If you have created messages in ERS that you want to send explicitly, proceed as follows:
    Select the menu path Logistics Invoice Verification ® Environment ® Messages ® Issue.
    Enter the message that you want to issue. You can enter the following criteria:
    Message data
    Message type (ERS, ERS6)
    Sending medium
    Creation date
    Processing mode
    Invoice document data
    Invoice document number
    Fiscal year
    Company code
    Invoicing party
    User
    Choose Execute.
    The system displays a list of the messages that correspond to the criteria.
    Select the message that you want to issue.
    Choose Execute.
    The system issues the messages and updates the list of messages. The system tells you how many messages were sent.
    Customer exit for changing output
    In the standard function modules for issuing print documents or creating IDocs for EDI, SAP enhancements exist in the form of customer exits. The enhancement MRMN0001 contains the following components:
    EXIT_SAPLMRMN_001:
    You can create additional IDoc segments for issuing an ERS document.
    EXIT_SAPLMRMN_001:
    You can change the structure and content of the print documents for the ERS document.
    Suresh

  • 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

  • I have a Problem in print the long description data through EDI.

    I have a Problem in print the long description data through EDI:Actually we want to print the long description data through EDI, but it not handling our huge long description data. Here is the example of that>We can print the first two lines into EDI output, but it is failing to print the below text: 
    <B>EPSON, TM-U590 Series: </B> Reliable 88 column slip printer. Operator friendly dot matrix impact printing. Ideal for hotel, bank, restaurant and many more applications .<br><BR> Includes: Printer, Black ribbon & a Connect-It Interface. Power Supply & interface cable sold separately. All printers are RoHS compliant & have a standard 1 year depot warranty. <BR> <BR>
       -------------------------------------Failing to print this lines------------------------------------------------------------------
    <b>COLORS:</b> Epson Cool White (ECW) Only<BR><BR><B><FONT COLOR=#FF0000#>Click links below for helpful Information</FONT><b><br><table border="0" bordercolor="" style="" width="100%" cellpadding="5" cellspacing="5"><tr><td><FONT SIZE="2"><CENTER><A HREF="www.sample.com"f.2605" target="_blank"><b>Spec Sheet</b></a></CENTER></FONT></td><td><FONT SIZE="2"><CENTER><A HREF="www.sample.com"f.2606" target="_blank"><b>MSRP Price List</b></a></CENTER></FONT></td><TD><FONT SIZE="2"><CENTER><A HREF="www.sample.com"f.2868" target="_blank"><b>Product Information Guide</b></a></CENTER></FONT></TD></TR><TR><td><FONT SIZE="2" COLOR=#0000FF><B>Warranty Information</B></FONT></td></tr><Tr><td><FONT SIZE="2"><CENTER><A HREF="www.sample.com"f.2554" target="_blank"><b>Depot Warranty</b></a></CENTER></FONT></td><td><FONT SIZE="2"><CENTER><A HREF="www.sample.com"f.2555" target="_blank"><b>Spare In the Air Warranty</b></a></CENTER></FONT></td><td></td></tr></table><br>
    Please provide some useful thoughts on this EDI issue.
    Thanks
    Ameer

    Try using the FM:
    ENQUE_READ2
    Passing the follwing values:
    GNAME --> VBAK (Sales Order header table)
    GARG   --> The lock argument
                       (This will be a combination of client number anb Sales Order No.
                        Eg: '3001210000054' where the first three digit i,e 300 is the client No
                       and 1210000054 is the sales order no.)
    Regards,
    Firoz.

  • Information to HMRC using EDI

    Hi,
    Please let me know if we can send industry tax information from oracle public sector financials to HMRC (Her Majesty revenue and custom) through EDI.
    It has been mentioned in th UG that oracle can send information to HMRC, but nothing has been mentioned about the format of the same.
    Any pointers or document in this regard would be very helpful.
    Thanks & Regards,
    Parag Gurjar

    Hi, Frisoni!
    The code is:
    Z PROGRAM
    DATA: l_verid TYPE verid.
    l_verid = 'TEST_DATA'.
    EXPORT l_verid TO MEMORY ID 'ZLSV_MOVEMENT_SF_LVERID'.
    After the export, sy-subrc = 0 (success)
    SMARTFORM
    DATA: l_verid TYPE verid.
    CLEAR l_verid.
    IMPORT l_verid FROM MEMORY ID 'ZLSV_MOVEMENT_SF_LVERID'.
    After the import, sy-subrc = 4 (error)
    I used many variations in sintax of the EXPORT / IMPORT commands and nothing worked.
    I also tried with SET PARAMETER / GET PARAMETER, and these commands didn't work too.
    Maybe the BAPI in the middle of the process is creating a new area in SAP memory, or a new thread... But I have no idea what is happening.
    Thanks!

  • Creation of Sales orders through EDI

    Hello,
    We have a problem when creating sales orders through EDI.
    We are getting IDOCs with a delay of 1 second.Before  
    creating sales orders through the posting function
    module IDOC_INPUT_ORDERS, we need to validate for
    reference Purchase order number in the IDOC. If there is
    any sales order in the database with the Purchase order
    number in the current IDOC that sales order should be 
    blocked.
    We already put a validation in the User-Exit of the
    posting function module. Because of the frequency of
    IDOCs we receive, this validation is getting failed.
    Can anybody tell me, how to process only 1 IDOC at any
    given point of time before the Posting process.
    Thanks,
    Madhusudan.

    Hi Sanjeev,
      Thank you very much for helping me out in this problem.Still I haven't got the solution.
    I tested the above mentioned configuration option by putting the Check Purchase Order Number field to 'A' in the transaction VOV8. But while creating sales orders, it is giving only information message. Is there any other way, to restrict the Duplicate PO value through configuration setup.
      can you also explain how to use Enqueue and Dequeue FMs in the inbound posting function module.
    Regards,
    Madhusudan.
    Message was edited by: Madhusudan Budati
    Message was edited by: Madhusudan Budati

  • Creation of Sales Order through EDI

    Hi
    Can anybody explain in detail the configuration steps involved in creating the sales order through EDI. If possible with screen shots.
    Points will be rewarded.
    Thanking you
    chan

    Hi Hari & Siva,
    Could you please send the document to my mail id
    [email protected]
    Thanks in advance
    MMVD

Maybe you are looking for

  • E-Recruiting search issue

    Hi All,    We are using webdynpro screens for e-Rec. The internal candidate is not able to see the job posting when we do a search. I tried all combinations possible. The search for external candidate i.e. unregistered candidate search and registered

  • Uploading Creative Webb cam software.

    While uploading Creative Web cam software, I received an error message indicating that the installation was cancled due to a "likely" Apple Quick time error. The error is not specifically stated. The message added that microsoft had researched the pr

  • Color Changes in Spry Data Fields

    Hi All, I'm new to Javascript & PHP  programming. Currently I have coded neccesary apperances for the Web  Page and also Spry Data Set to read an external XML date source file. What I need  to do is one of the fields, needs to have color based status

  • HT4623 6.1.3 update issue with iPhone 5

    I Cannot update my iPhone 5 to the latest software 6.1.3! The option install now is greyed out any ideas?

  • Is my Ipod 2nd generation now obsolete?

    I want to chat to Apple support about my iPod but the serial number is not recognised (I've tried all possible combinations and used a magnifying glass).  The iPod has not been used for quite a long time - is it now considered obsolete or something?