Outbound Pexr2002

We have a lot of Outbound Interfaces from SAP which require the payment information ( REGUH REGUP PAYR, BSAK, BSEG details). Is there a way we can configure SAP so that every payment run ( f110 ) would create Outbound IDOCS for all the payment types ( checks , etf, wires,etc ).
I am aware of the EDI settings for checks but then I wanted to integrate all the thre payment methods so that whenever F110 is executed I generate a PEXR2002 which I assume will contain all the necessary fields and the EAI tool then can pick relevant fields.
Please advise. ( Will the program RFFOALE1 be of any help in this regard ?
Rgds,
Ajay

HI,
You need to maintain the following configuration,
SPRO-> Financial Accounting-> AR and AP -> Business transactions -> Outgoing Payments -> Automatic Outgoing Payments -> Payment Media -> EDI Payment orders and debit memos -> Define EDI compatible Payment methods for a house bank
Once you enable a payment method for EDI, it can be included in the Payment IDOC.
The program to use for creation of IDOC in F110 is RFFOEDI1.
Regards

Similar Messages

  • IDOC Type PEXR2002: Txn F110

    Hi Idoc Gurus,
    I have to trigger the IDOC PEXR2002 type for payment run transaction F110.
    I know there is this program RFFOEDI1 which does this job.
    My questions are :
    1) Do I have to create a Outbound Processing type ? Or it is not required as the program already does the job ?
    2) Are all relevant data populated by that program ?
    3) If I have to populate the Z-extensions of the IDOC type PEXR2002, then which is the user-exit I should use ?
    Any hints will be greatly appreciated.
    Regards,
    Sandip.

    Check the links -
    https://forums.sdn.sap.com/click.jspa?searchID=2815420&messageID=3492865
    Outbound PEXR2002
    Regards,
    Amit

  • Outbound - 820 - PEXR2002

    Hi,
    I'm using IDOC PEXR2002 & message type PAYEXT for outbound 820. I need to provide Invoice Header Text in the itme level data, but the Idoc doesn't return this. Please advise.
    Regards,
    Gajendra

    if any of your required fields are not available in IDocs then you should extend the idoc.
    Please go thru the steps provided in the Book "ALE/EDI and IDoc Technologies for SAP" By Arvind Nagpal..
    Also check the knowlege pool
    http://help.sap.com
    Cheers,
    Abdul Hakim
    Mark all useful answers...

  • Automated error email notification when outbound IDOC fails

    Hi,
    The requirement is that whenever the outbound IDOC of message type PAYEXT, basic type PEXR2002, fails, then email has to be trigerred to a group id.
    I had suggested to write a report program that runs as a job. If the IDOC goes to error status then mail will be sent from this report. Client prefers it to be done through workflow.
    There is a standard process code for outbound IDOC failure handling EDIO (we40). standard task 7989 has been assigned to this process code. I dont want to modify this standard task as I am not sure of impact.
    Terminating event for this task is 'ERRORPROCESSCOMPLETD'.
    I have developed the workflow that has trigerring event 'ERRORPROCESSCOMPLETD' and bound with the IDOC number. This will send mail to the group id with the IDOC details
    Now issue is that, I am not sure if standard process EDIO will be trigerred automatically, or should we configure anywhere. Since this is standard outbound IDOC, I am not able to add the process code in partner profile.
    Please give your inputs or any other alternate solution to send mail through workflow when  outbound IDOC fails.
    Thanks in advance.

    Hi,
    I guess in your outbound partner profile for PAYEXT. you need to add process code  EDIO in message control TAb. WHich will cause to trigger the workflow which will send the notification.

  • Include segment in Control record of  idoc type PEXR2002 and PAYEXT

    Gurus
    This is business scenario. We are using four different flavours of payment methods. when exectuing F110 for each payment method,Program RFFOEDI1 generates IDOC. This IDOC are send to EDI team who then sends that as EDI820 to bank.
    The payment method used are populated in Detail record field of IDOC . But EDI team wants that to be in Control record of IDOC .
    We are using PEXR2002 and message type is PAYEXT . this is an outbound IDOC .
    Is it possible to add segement in control record for each payment method?.
    Thanks for your time and consideration
    Auroar

    It may depend on how the IDoc is created.
    From a file.
    Sent via a Remote Call.
    You would then need to code it for this Message type only.
    I would take a copy of the standard Function and change that. You would have greater control then.
    Why is the partner number wrong anyway. Can you not just create another partner profile(s).
    Message was edited by:
            Martin Shinks

  • EDI 820 Outbound Payment advice EUPEXR

    When I am trying to generate an EDI through payment run F110, it correctly generates one for Message type PAYEXT and Idoc Basic type PEXR2002. However, in addition to that it is generating one for Message type EUPEXR and Idoc Basic type IDCREF01.
    What is the purpose of this EUPEXR and why is it generating even though I havent set it up in the Outbound parameters of the Partner profile?
    Thanks!

    Have you checked this thread in SDN?
    PEXR 2002, Stopping generation of EUPEXR inbound message type.
    This is automatically generated by SAP, and deals with the eletronic signature details usually accompanying an electronic payment instruction set. The thread gives a way to prevent output of the IDoc (not preventing generation through!).
    The Building Block documentation for In-House Cash clearly states:
    When you create PAYEXT, EUPEXR is created automatically. Recommendation: Create a port to which EUPEXR can be sent, if you do not need this Idoc type in SAP In-House Cash. You can delete this file defined for the port at specific intervals.
    Rgds
    Gulshan

  • IDOC PEXR2003 vs PEXR2002

    How do i know which IDOC basic type i should be using for message type PAYEXT? What are the different basic types available for outbound payment document to be sent to the bank

    Hi,
    I never recommended PEXR2003. I simply mentioned that 2003 includes all segments of 2002 + newly added segments.
    Now, it depends on business which it'd like to go for. We''ve implemented PEXR2002, which satisfies all our need.
    Thanks,
    Nirav

  • Implementation of IDOC types FINSTA01 and PEXR2002

    Hi All,
    I want to implement the 2 IDOC types PEXR2002 and FINSTA01 using EDI.The requirement is like I have to generate both the inbound and outbound processing for both the IDOC types using EDI.
    I have the following queries :
    1)What are the basic fields that are required for both the inbound and outbound processing(like file format)
    2)How the inbound and outbound processing will be triggered like how can I send the file from SAP to EDI or how can I get the file from EDI to SAP and how to uplaod the record into SAP is there any SAP standard transactions or any standard reports or do I have to configure in the SPRO etc.
    3)What are the settings that I have to configure?
    Please help me out and your help will be appreciated.
    Thanks and Regards,
    Ramesh.

    Hello Ramesh,
    The answers to your questions are a few chapters in some books, meaning its quite large.
    But in short.
    1. the minimum fields are what is required by that particular transaction in SAP for inbound and for outbound you gotta check with the receiving party what they need.
    example , if you are posting a PO in SAP, then what are the mandatory fields, thats the minimum.
    With every idoc , incoming, there are a few ways to post, most common is via function modules.
    Lets say you know a partner which will communicate via EDI, you have to maintain a partner profile in WE20.
    There you define the incoming and outgoing messages.
    Every message has, idoc type.
    Transactions WE42 and WE43 are where you define a process code for attaching the message type/idoc type to a Funtion module.
    Also there is config for setting up output types, see transaction NACE.
    This is a process with lots of parameters.
    You would be better off getting a book which explains it all in a proper order.

  • FM for outbound payment idoc

    Hi,
    How do we find out the FM for outbound payment idoc?.Here are the details
    Message type-PAYEXT
    Idoc type-PEXR2002
    Thanks,

    This thread is was last replied more than a year ago, but I'll add a little just to contribute.
    WE60 documentation for the IDocs don't really give much except field / segment
    information,  but don't talk about where the fields come from.
    FI_EDI_PAYEXT_PEXR2001_OUT seems to be the right FM, not sure how it relates to IDoc type pexr2002 as 2001 is the older version, but perhaps it handles the difference somewhere inside.
    As to where certain segment fields come from (i.e. the mapping to master data fields...) , I've been debugging and still in progress.
    I have not been able to find any straight forward mapping, and my comments at the moment are:
    For any particular segment field of PEXR2002, take a look at FM :
    FI_EDI_PAYEXT_PEXR2001_OUT
    to see how it populates the field.  Chances are, the values come from the tables REGUH/REGUP/REGUV.
    The payment run process as far as my knowledge is concerned is as follows:
    1) Payroll Run -> Stores to table BT
    2) Pre DME (e.g. trx PC00_M08_CDTA) picks data frm BT and creates payment data in REGUH / REGUP / and REGUV tables. This gives you an identification feature ID for the next step.
    3) RFFOEDI2 changes status field in REGUH for particular payment data record based on ID from step 2.. this enables it to be picked up in the next step.
    4) RFFOEDI1 converts the record in REGUH into an IDoc which can be processed in BD87.
    I have debugged from step 4 backwards to step 3, i.e. I know that segment field X comes from REGUH field Y. Now I have to debug step 2 to find out how it populates REGUH field Y. If this comes directly from master data, then that makes life easier. But if this REGUH field Y comes from table BT of step 1, then perhaps I have to debug the payroll run somewhere. (Nightmare?
    Anyway, if anyone knows better, please advise.

  • To seperate PAYEXT outbound IDoc according to message type

    Gurus
    This is business scenario. We are using four different flavours of payment methods. when exectuing F110 for each payment method,Program RFFOEDI1 generates IDOC. This IDOC are send to EDI team who then sends that as EDI820 to bank.
    The payment method used are populated in Detail record field of IDOC . But EDI team wants that to be in Control record of IDOC .
    We are using PEXR2002 and message type is PAYEXT . this is an outbound IDOC .
    I want to know whether Message code given for PAYEXT and how to link that with Payment Method?
    Is it possible to add segement in control record  and to map that to each payment method?
    Your reply would highly help me to slove out the problem
    Thanks
    Auroar

    Hi Auro,
    You use use EDI_DC-SNDSAD field, currently this field is used no where.
    If you not sure where to see double control record and click address info tab
    you can use either field receiver or sender.
    For testing use WE19 transaction and pass your paymethod to following field
    and then inform to EDI Mapper that your sending paymethod in this field.
    For them this field is very easy to grab.
    Let me know if you any concern.
    Thanks,
    Narayan

  • Trigger  outbound idoc for F110 program

    Hi Experts,
                      I am new to idocs, please anybody can help
    regarding to create outbound idocs when i run F110 program.
    when  i run F110 with parametrs company code and payment method, automatically it will create idoc and send it to partner system.
    i think i have to use pexr2002 and message type payext.
    please help me on my request, it is very urgent work.
    Regards,
    Venkata

    Follow the steps:
    1) Do relevant Settings for payment program ( FBZP).
    2) Example: For the house bank you have to set the EDI partner profile no. and the EDI partner profile and EDI compatible payments methods.you have to attach the payment methods to the house bank EDI profile. And check generate
    EDI immediately in we20.
    3) Create the partner profile for bank with message type " PAYEXT", partner
    type " B". AND THE IDOC BASIC TYPE AS " pexr2002".
    4) when you run the payment, the IDOC will be generated.
    REfer to:
    http://help.sap.com/bp_bblibrary/500/Documentation/W25_BB_ConfigGuide_EN_US.doc
    http://www.sap.com/usa/solutions/business-suite/erp/financials/pdf/BWP_%20SAP_In-House_Cash.pdf
    Reddy

  • FI Invoices Outbound - Any Standard Program ?

    Hi,
      Is there any Standard program to send SAP FI Open, Chnaged and Closed Invoices in to a File (Outbound)?
    How to Track Invoice is new or chnaged or closed ?
    I appricate any help. Thank you.

    i am away from my system...Just check BKPF / BSEG tables...U can get the field name....
    Award points if useful...

  • How to compare delivery date in schedule lines and PGI in outbound delivery

    Hi,
    I want to create a report to monitor and compare different dates in sales and delivery process.
    One of my key figure is the comparison between date confirmed to the customer, that I can find in the schedule line of the sales order, and the actual goods issue date from the outbound delivery.
    But I can't succeed in making the link between delivery and schedule lines, means between LIKP and VBEP.
    Would you have any idea?
    Thank you.

    It seems there's no exact (table) connection / link between delivery item and schedule line item.
    Those who were searching for this thing (link / connection between delivery item and schedule line) were recommended to use FM "RV_SCHEDULE_CHECK_DELIVERIES".
    This FM calculates the delivered quantity for each schedule line, so it makes link between the delivery item and schedule lines - however if you check the code it's quite sophisticated...
    (if you put a breakpoint in the FM and display a SO in VA03, you can check how the parameters have to be populated with data).
    Schedule Line and Delivery Link
    Edited by: Csaba Szommer on Aug 5, 2011 12:03 AM

  • Getting error while testing a outbound file in oracle B2B11g

    Hi,
    I am trying to configuare a outbound scenario in oracle B2B 11g.
    I have created .ecs file and .xsd file and created a document type also and i am using generic file 1.0 as a lintening channel protocol and trying to read the input xml document from a perticular path.
    I had setup partner and agreement also. everything is working fine and also file is succesfully polling from the source folder but i am getting error in B2B as :
    B2B-50083
    Error Description Machine Info: (infva0325) Description: Document protocol identification error.
    Error Level ERROR_LEVEL_COLLABORATION
    Error Severity ERROR
    Error Text Document protocol identification error.
    Can anyone guide me how to resolve this error?
    I had tried everything but of no use.
    Please do reply me with your suggestions.

    Hi Anuj,
    Please find below xml data which will be saved as .txt file for outbound processing. Let me know if there are any changes i have to do. Please let me know if you need any further information. Listening channel is reading the file but in agreement level it is failing.
    <?xml version="1.0" encoding="UTF-8"?><Transaction-DESADV XDataVersion="1.0" Standard="EDIFACT" Version="D93A" CreatedBy="ECXEngine_837" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" CreatedDate="2011-12-14T12:59:40" GUID="{2d323135-3336-3630-3232-313938393033}" xmlns="urn:oracle:integration:b2b:099C29D4C4ED419194917C20ADF8ABC3">
    <Internal-Properties>
    <Data-Structure Name="Interchange">
    <Property Name="InterchangeSenderID">senderID</Property>
    <Property Name="InterchangeSenderQual">senderQuali</Property>
    <Property Name="InterchangeReceiverID">RecieverID</Property>
    <Property Name="InterchangeReceiverQual">RecieverQuali</Property>
    <Property Name="RepeatingSeparator"/>
    <Property Name="InterchangeApplicationRef">DESADV</Property>
    <Data-Structure Name="Transaction">
    <Property Name="TransactionID">DESADV</Property>
    <Property Name="TransactionControllingAgency"/>
    <Property Name="TransactionMessageVersionNumber">D</Property>
    <Property Name="TransactionMessageReleaseNumber">93A</Property>
    <Property Name="TransactionAssociationAssignedCode"/>
    </Data-Structure>
    </Data-Structure>
    </Internal-Properties>
    <Segment-UNH>
    <Element-0062>#ControlNumber#</Element-0062>
    <Composite-S009>
    <Element-0065>DESADV</Element-0065>
    <Element-0052>D</Element-0052>
    <Element-0054>93A</Element-0054>
    <Element-0051>UN</Element-0051>
    <Element-0057>EDIT30</Element-0057>
    </Composite-S009>
    </Segment-UNH>
    <Segment-BGM>
    <Composite-C002>
    <Element-1001>351</Element-1001>
    </Composite-C002>
    <Element-1004>3364382</Element-1004>
    </Segment-BGM>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>137</Element-2005>
    <Element-2380>20111214</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    <Loop-Group_2>
    <Segment-NAD>
    <Element-3035>SH</Element-3035>
    <Composite-C082>
    <Element-3039>7393142020009</Element-3039>
    <Element-1131 xsi:nil="true"/>
    <Element-3055>9</Element-3055>
    </Composite-C082>
    </Segment-NAD>
    </Loop-Group_2>
    <Loop-Group_2>
    <Segment-NAD>
    <Element-3035>CN</Element-3035>
    <Composite-C082>
    <Element-3039>7350056030012</Element-3039>
    <Element-1131 xsi:nil="true"/>
    <Element-3055>9</Element-3055>
    </Composite-C082>
    </Segment-NAD>
    </Loop-Group_2>
    <Loop-Group_10>
    <Segment-CPS>
    <Element-7164>1</Element-7164>
    </Segment-CPS>
    <Loop-Group_15>
    <Segment-LIN>
    <Element-1082>1</Element-1082>
    <Element-1229 xsi:nil="true"/>
    </Segment-LIN>
    <Segment-PIA>
    <Element-4347>5</Element-4347>
    <Composite-C212_1>
    <Element-7140>210587</Element-7140>
    <Element-7143>BP</Element-7143>
    </Composite-C212_1>
    </Segment-PIA>
    <Segment-QTY>
    <Composite-C186>
    <Element-6063>12</Element-6063>
    <Element-6060>3</Element-6060>
    </Composite-C186>
    </Segment-QTY>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>PK</Element-1153>
    <Element-1154>1</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>VN</Element-1153>
    <Element-1154>6152310</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>171</Element-2005>
    <Element-2380>20111214</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_23>
    <Segment-QVA>
    <Composite-C279>
    <Element-6064>0</Element-6064>
    <Element-6063_1>83</Element-6063_1>
    </Composite-C279>
    <Element-4221>CP</Element-4221>
    </Segment-QVA>
    </Loop-Group_23>
    </Loop-Group_15>
    <Loop-Group_15>
    <Segment-LIN>
    <Element-1082>2</Element-1082>
    <Element-1229 xsi:nil="true"/>
    </Segment-LIN>
    <Segment-PIA>
    <Element-4347>5</Element-4347>
    <Composite-C212_1>
    <Element-7140>210510</Element-7140>
    <Element-7143>BP</Element-7143>
    </Composite-C212_1>
    </Segment-PIA>
    <Segment-QTY>
    <Composite-C186>
    <Element-6063>12</Element-6063>
    <Element-6060>3</Element-6060>
    </Composite-C186>
    </Segment-QTY>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>PK</Element-1153>
    <Element-1154>1</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>VN</Element-1153>
    <Element-1154>6152310</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>171</Element-2005>
    <Element-2380>20111214</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_23>
    <Segment-QVA>
    <Composite-C279>
    <Element-6064>0</Element-6064>
    <Element-6063_1>83</Element-6063_1>
    </Composite-C279>
    <Element-4221>CP</Element-4221>
    </Segment-QVA>
    </Loop-Group_23>
    </Loop-Group_15>
    <Loop-Group_15>
    <Segment-LIN>
    <Element-1082>3</Element-1082>
    <Element-1229 xsi:nil="true"/>
    </Segment-LIN>
    <Segment-PIA>
    <Element-4347>5</Element-4347>
    <Composite-C212_1>
    <Element-7140>081349</Element-7140>
    <Element-7143>BP</Element-7143>
    </Composite-C212_1>
    </Segment-PIA>
    <Segment-QTY>
    <Composite-C186>
    <Element-6063>12</Element-6063>
    <Element-6060>1</Element-6060>
    </Composite-C186>
    </Segment-QTY>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>PK</Element-1153>
    <Element-1154>2</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>VN</Element-1153>
    <Element-1154>6152310</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>171</Element-2005>
    <Element-2380>20111214</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>NB</Element-1153>
    <Element-1154>JF074</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>21E</Element-2005>
    <Element-2380>20160905</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_23>
    <Segment-QVA>
    <Composite-C279>
    <Element-6064>0</Element-6064>
    <Element-6063_1>83</Element-6063_1>
    </Composite-C279>
    <Element-4221>CP</Element-4221>
    </Segment-QVA>
    </Loop-Group_23>
    </Loop-Group_15>
    <Loop-Group_15>
    <Segment-LIN>
    <Element-1082>4</Element-1082>
    <Element-1229 xsi:nil="true"/>
    </Segment-LIN>
    <Segment-PIA>
    <Element-4347>5</Element-4347>
    <Composite-C212_1>
    <Element-7140>051596</Element-7140>
    <Element-7143>BP</Element-7143>
    </Composite-C212_1>
    </Segment-PIA>
    <Segment-QTY>
    <Composite-C186>
    <Element-6063>12</Element-6063>
    <Element-6060>1</Element-6060>
    </Composite-C186>
    </Segment-QTY>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>PK</Element-1153>
    <Element-1154>2</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>VN</Element-1153>
    <Element-1154>6152310</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>171</Element-2005>
    <Element-2380>20111214</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_16>
    <Segment-RFF>
    <Composite-C506>
    <Element-1153>NB</Element-1153>
    <Element-1154>116812505</Element-1154>
    </Composite-C506>
    </Segment-RFF>
    <Segment-DTM>
    <Composite-C507>
    <Element-2005>21E</Element-2005>
    <Element-2380>20150131</Element-2380>
    <Element-2379>102</Element-2379>
    </Composite-C507>
    </Segment-DTM>
    </Loop-Group_16>
    <Loop-Group_23>
    <Segment-QVA>
    <Composite-C279>
    <Element-6064>0</Element-6064>
    <Element-6063_1>83</Element-6063_1>
    </Composite-C279>
    <Element-4221>CP</Element-4221>
    </Segment-QVA>
    </Loop-Group_23>
    </Loop-Group_15>
    </Loop-Group_10>
    <Segment-CNT>
    <Composite-C270>
    <Element-6069>2</Element-6069>
    <Element-6066>4</Element-6066>
    </Composite-C270>
    </Segment-CNT>
    <Segment-UNT>
    <Element-0074>#SegmentCount#</Element-0074>
    <Element-0062>#ControlNumber#</Element-0062>
    </Segment-UNT>
    </Transaction-DESADV>

  • Intrastat - Inbound/Outbound of non valuated materials used in production.

    Hello everyone,
    I've found several threads and very useful posts (ex: Re: PO Creation of free goods for intrastat reporting)  regarding similar issue, but the solution proposed was manual input, therefore not answering totally to my client requirement.
    I am actually performing maintenance activities and there is this new business process, I have been searching for the correct understandind of this process regarding intrastat here and I haven't found.
    So i will describe the process hoping that someone can give me some hint:
    Vendor A
    Customer B
    Raw Material R
    Finish Product P
    Service S
    1. So we ( Vendor A ) receive raw material from our Customer B (+mov.type +)
    2. We ( Vendor A ) with a production order process the Raw material R into Finish Product P.
    3. We ( vendor A ) send the Finish Product P back to the Customer B.
    4. We ( Vendor A ) then issue an invoice for the Service S to the Customer B.
    5. It can occur that we Vendor A, can send back the Raw material R which was not manufactured back to Customer B (with a mov type.)
    So thiswas the scenario and how the process is beeing done, and the client understanding is:
    - As far as i understood, (please correct me if i am wrong) the Raw Material R must be declared (Quantity and statistic value) in Purchasing Intrastat, in the transactions where the Vendor A receives the raw material and as well in the case that they send it back to Customer B.
    - Regarding the Invoice from the Vendor A to Customer B, the Raw Material R is incorporated in the Finish Product P, therefore I've been told that, the Statistic Value determined in the invoice in this situation has to include the cost value of the raw materials R.
    My issues in MM are the following:
    1 - If Raw Material R is non valuated, how can i maintain its statistic value to be declared, in inbound as well outbound? as an Info-record?
    My issues in SD are the following:
    1 - If the Statistic Value GRWR can be for example 102% calculated over the net value, and if the cost value of Raw Materials R are to be included, so i would have to add them somehow to the statistic value.
    In this case the question comes up, where do i maintain the value of the raw materials R, and how to add it to the statistic value automatically ?
    Regarding what is implemented in this client, they have SD intrastat running, but not MM intrastat was implemented.
    Feedback would be highly appreciated!!
    Thank you in advance.

    Hi Sergio,
    I have this exact same requirement but on a bigger scale.
    The complexities are:
    1. The raw material which client use, that can be either supplied by customer or can be procured by client. Remember, customer's raw material and my externally procured raw material is exactly same in all properties.
    2. There are many customers who send same exact raw material.
    Requirements:
    1. Client wants to use same material codes (for raw materials and even for finished products) for normal production cycle and for Job work cycle. Master data needs to be the same, and data need to be separated at transaction level.
    2. Whatever raw material client gets from customer, its statistical value should be entered at the time of goods receipt.
    Please suggest if preference processing can handle this.
    Thanks & Regards,
    Vishal

Maybe you are looking for