PAYEXT IDOC Enhancement for Japan

Hi
We are looking to enhance the PAYEXT IDOC - for Japan. Can anyone tell me the program/function module that is triggered to create PAYEXT IDOC from F110.
Appreciate your help!
Regards

HI,
RFFOEDI1 is the program which creates PAYEXT IDOC you can configure this through FBZP transaction.
Inorder to to execute this program RFFOED11 through F110.
Regards,
Shanmugavel Chandrasekaran

Similar Messages

How to find idoc enhancements

Hello Friends,
Could any body please let know how to find idoc enhancements.
for inbound and outbound. Already i had searched in forum.
regards,
phani

HI ,
u can follow the steps:
Transaction: SMOD
Click F4 help for Enhancement
Path: F4help -> SAP Applications -> Logistics general -> Logistics Basic Data ->
Business partners -> Vendor Master.
Find the enhancement as VSV00002, which is an approximate user exit.
Now search for different extensions like VSV00001. Then see for its components.
Identify the appropriate user exit to be u2018EXIT_SAPLVV01_001u2019 (Create Export of
Additional Customer Master Segments). This user exit can be used in outbound ALE
process, meant for filling the data into custom segments.
You have to identify here another user exit as u2018EXIT_SAPLVV02_001u2019, which is
helpful for inbound ALE process. This user exit can be used to read the segments
and post it to Application repository.
Step9: Develop a project to encapsulate enhancements and components.
Transaction: CMOD.
Enhancement: custex and click Create to provide attributes.
Click Enhancement Assignments.
Provide VSV00001, short text and save.
From the initial screen of the transaction, select components and click change.
Find 4 components to be added.
Activate them.
Select user exit EXIT_SAPLVV01_001 for outbound process and double click it. It leads to function builder.
Double click on provided include program ZXVSVU01 and press enter.
Now, write supporting code for IDoc extension, i.e., populating custom segments in IDoc.
Check the code and activate.
Thanks
Shambhu

Creating DMEE file as well as an outgoing PAYEXT idoc for payments

We have everything set up for the creation of the DME file in the DMEE. The file is also getting created in one of the directories. Now one of the requirements is to create a PAYEXT idoc for the same information in the payment run? Can someone let me know if both DME file and also the PAYEXT idoc could be created simultaneously for the same payment run? if so, please give the steps to be used for configuration.
I have run the program RFFOEDI1 and RFFOEDI2 for the payment run, both of them say "NO records selected"
Thanks in Advance
Raj.

Hi Lailu,
You need to use the Message Type PAYEXT for the payment run with the transaction F110.
There will be a house bank associated with the company code and that house bank has to be EDI enabled first.
I believe you need to send the Payments to the bank, in that case the partner profile has to be created with partner type B(Bank). Usually we do all the payments through Bank, so the payments has to be sent to Bank.
I think I have answered your question.
Thanks,
Mahesh.

Bapi for PAYEXT IDOC

Hi,
Is there a BAPi which has he functionality of PAYEXT IDOC?
Help is much appreciated
Jeff

Hi Alejandro,
Did you use process code <b>DELV</b> (IDOC_INPUT_DELVRY) for message type WHSCON and IDoc type DELVRY03/DELVRY01?
Hope this will help.
Regards,
Ferry Lianto

Enhancement for IDOC

Hi,
I have to extend IDOC INVOIC02 to have additional segments. I will develop the segments. But for writing the code to fill in those segments, I need to find the user exit. Anyone has come across such a requirement...please help me with it..

Hi Gurus,
I'm not sure if I would hear Vijay.
I'm facing issue with Idoc type INVOIC01 and Also i extend this Idoc(INVOIC01) for few of custom fields.
I know I have to populate data and append in idoc_data.That i have done.
Process Code id SD09 and FM is IDOC_OUTPUT_INVOIC.
But once Iu2019m calling VF02 and generating the messages via EDI itu2019s neither getting trigger nor Filling the custom IDOC.
I tried my code in all below three exits but No Luck.
EXIT_SAPLVEDF_001
EXIT_SAPLVEDF_002
EXIT_SAPLVEDF_003
Any suggestions would be highly appreciable.
Thank you,
Amit

Payment requests created from In-House Cash - error with PAYEXT IDOC

Hello -
I am getting getting a '51' error with my inboud PAYEXT IDOC and the payment request cannot be created and the IDOC error is : Error creating the payment requests - no valid payment method available.
I have checked the Route process config in IHC and it looks good (or I think so). I then checked the IHC config: Set Up of payment request for inbound IDOC in FI and am wondering about the Processing Parameters set up. In this config, I see 2 payment methods field (Payment Method for This Payment) and (List of the Payment Methods to be Considered).   Can somebody tell me what's the difference between these two fields and since my payment method is not in the List of PM to be considered, could that be causing my erorr?
Any guidance would greatly be appreciated.
Thanks
Becky

Hi Odaiah
I am in ECC 5.0 and when I view IMG activity IHC_VC_INB_CUST, there's a field called:
Payment Method for This Payment(Payment method used to settle open items)
and another field called List of the Payment Methods to be Considered.
The invoice was paid via payment method 'W' and in our system, we are using IHC to make payments on behalf. So after running F110 for payment method 'W', the IDOC gets created and sent to IHC to process. IHC will then create the payment request (IDOC PAYEXT) which will then get process by F111. Since the IDOC is failing, the payment request is not getting created.   You mentioned to get an ABAPer to throw in debug, I would love to but does not know the program that this process is running through. I tried putting it in debug from WE02 (IDOC processing) but with no success.
Becky

Payext Idocs Issue

Hi,
I am generating payext idocs off the back of a payment run (F110). The issue that I have is where I am paying a supplier with multiple invoices, that the individual invoices are all included in the IDOC. When the bank statement is returned to us, for this type of example, the bank statement is delivering all of the invoice references in the Payment Notes section. I am being informed that this is due to my system sending out segments E1EDP02 009 / 010. I am also informed that I need to make changes in FBZP - "Payment methods in Company Code". So far my settings (under payment advice control) here are:-
1. Note to payee lines on form - None
2. Payment Advice output according to number of lines - always payment advice
Also in the DME I am using program RFFOEDI1 and have amended the variant in the output control section to only generate 2 "number of " invoice details.
Is anyone able to advise please.

Hi,
This thread has been created some time ago and recieved no response. Can you please close if you feel this issue/query has been resolved in the meantime. If it has not then please provide additional information in relation to your query. By providing updates to your thread it moves you thread to the first page of thread and increases visibility and possiblity for the multiptude of experts in SDN Forums to offer their support.
Therefore please update with more information or close thread.
Thank you for your assistance.
Regards,
Brendan.
(ERP FI/CO SDN/WIKI Moderator)
http://wiki.sdn.sap.com/wiki/display/ERPFI/ERP+Financials

Enhancement for VL32N

Hi,
In vl32n transaction when we save the particular inbound delivery
I want to perform material to material transfer posting by triggering MIGO transaction and changing the batch number .
Can u suggest any enhancement for this requirement?

Hi,
Check if any of the following are useful to you:
V02V0001 Sales area determination for stock transport order
V02V0002 User exit for storage location determination
V02V0003 User exit for gate + matl staging area determination (h
V02V0004 User Exit for Staging Area Determination (Item)
V50PSTAT Delivery: Item Status Calculation
V50Q0001 Delivery Monitor: User Exits for Filling Display Fields
V50R0001 Collective processing for delivery creation
V50R0002 Collective processing for delivery creation
V50R0004 Calculation of Stock for POs for Shipping Due Date List
V50S0001 User Exits for Delivery Processing
V53C0001 Rough workload calculation in time per item
V53C0002 W&S: RWE enhancement - shipping material type/time slot
V53W0001 User exits for creating picking waves
VMDE0001 Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 Shipping Interface: Message SDPACK (Packing, Inbound)
Regards,
Renjith Michael.

Outbound output type & Idoc type for MIRO (Invoice Posting)

Hi Gurus,
I have requirement like , I want to send the outbound IDoc to a external system containg the invoice detials after Saving in MIRO.
I am not able to find any output type & Idoc type for the same.
By going through varios threads , I found that there tell there is no Idoc type & output type for sending Idocs after MIRO.
Kindlt let me know, if it so, or how this req can be fullfiled by other ways.
Thanks
Amresh

Hi,
Create Custom Idoc type with required fields,custom output type and assign it to partner profiles.(If there is no std idoc type or output type)
Use Funtion module MASTER_IDOC_DISTRIBUTE to generate Idocs while saving MIRO, for this you need to find exit or implement implicit enhancement while saving MIRO.
Regards,
Ashok.

Enhancement for t.code FBRA

Hi,
I tried using user-exit F050S006. i inserted a break-piont in the exit and executed transaction code FBRA but control doesnt go to this exit. please help me out in finding an enhancement while executing FBRA.
Regards,
Sonali.

hi,
check this
Enhancement
F050S003                                FIDCC2: Change IDoc/do not send
F050S002                                FIDCC1: Change IDoc/do not send
F050S001                                FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
SAPLF051                                Workflow for FI (pre-capture, release for payment)
RFKORIEX                                Automatic correspondence
RFEPOS00                                Line item display: Checking of selection conditions
RFAVIS01                                Customer Exit for Changing Payment Advice Segment Text
F050S004                                FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
F050S005                                FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
F050S006                                FI Outgoing IDoc: Reset Clearing in FI Document
F050S007                                FIDCCH Outbound: Influence on IDoc for Document Change
F180A001                                Balance Sheet Adjustment
FARC0002                                Additional Checks for Archiving MM Vendor Master Data
FEDI0001                                Function Exits for EDI in FI
Business Add-in
FI_FB08_SUBST_BUDAT                     FB08: Check Posting Date for Reversal of FI Doc. with FB08
FI_GET_INV_PYMT_AMT                     BAdI for determining the payment amount for an invoice
FI_HEADER_SUB_1300                      Screen Enhancement for Document Header SAPMF05A
FI_PAYREF_BADI_010                      BAdI: Payment Reference Number
FI_RES_ITEM_CURRENCY                    Document of Residual Item with Invoice Currency
FI_TRANS_DATE_DERIVE                    Derive BKPF-WWERT from Other Document Header Data
BADI_ENJ_ALT_ADR                        Go to alternative vendor/customer data
BADI_F040_SCREEN_600                    Screen Enhancement on F040 0600 Document Header
BADI_FDCB_SUBBAS01                      Screen Enhancement 1 on FDCB Basic Data Screen (010, 510)
BADI_FDCB_SUBBAS02                      Screen Enhancement 2 on FDCB Basic Data Screen (010, 510)
BADI_FDCB_SUBBAS03                      Screen Enhancement 3 on FDCB Basic Data Screen (010, 510)
BADI_FDCB_SUBBAS04                      Screen Enhancement 4 on FDCB Basic Data Screen (010, 510)
RFESR000_BADI_001                       BAdI for Own Processing of POR Item
BADI_FDCB_SUBBAS05                      Screen Enhancement 5 on FDCB Basic Data Screen (010, 510)
BADI_MIRO_SPLT_ADD                      Append additional fields of ACCVS to ACCIT
BADI_PRKNG_NO_UPDATE                    BAdI for Deactivating Update of Parked Documents
FVFZ                                    Replacement for Function Modules of Function Group FVFZ
INVOIC_FI_INBOUND                       BADIs for Inbound IDoc INVOIC FI (Vendor Invoice)
F050S008                                FIDCC1, FIDCC2 Inbound IDoc: Update Comparison Ledger
AC_QUANTITY_GET                         Transfer of Quantities to Accounting - Customer Exit
ADJUST_NET_DAYS                         Change to Net Due Date
FBAS_CIN_LTAX1F02                       Tax interface
FBAS_CIN_MF05AFA0                       EWT - Downpayment Clearing - Tax transfer for CIN
FISPLIT                                 Online Split: Cash Discount, Exchange Rate Differences
FI_AUTHORITY_ITEM                       Extended Authorization Check for Document Display (FB03)
FI_DOC_DISP_LI                          Diversion to Document Items (FB03)
Yogesh N

Idocs - Enhancements!

Hi Friends!
    Can any one pls tell what all the enhancements which u ve worked on IDOCS.
    Pls give step by step detail in Creation of segments & FM coding Please.
   Looking for your Help.
   Thanks In Advance.
    Rahul.

Hi Rahul..
These are the Steps for IDOC enhancement.
IDOC EXTENSIONS
SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02.
By extending the Basic IDOC type, you are actually creating a new IDOC type.
You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note: that you should not add fields to existing segments but should create a new segment and associate it with an existing segment.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address DEBMAS02 does not have a segment or fields that communicate the contact persons business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Reward if Helpful

How to find the number of idocs generated for a customer on the basis of his purchase order in a day ?

How to find the number of idocs generated for a customer on the basis of his purchase order in a day ?

Dear Friends,
I am absolutely agree with your answer .
But my question is,
Lets say.....
One customer sending X number of purchase orders in a day , so how many IDocs generated on that specific day for that specific customer .
So, Question is , How can we find the no of sales orders(IDocs) generated for the customers on the specific day ?
Hope you all understood my requirement .
Thanks & Regards,
Aditya

BCExeption: The IDOC metadata for null is not available in SID

<h3>Hello Guys,</h3>
we need some information about the error message:
com.wm.pkg.sap.BCExeption: The IDOC metadata for null is not available in <SID>
We use a Business Connector 4.8 and the backend is an ECC 6.0, we have an inbound xml scenario with FTP.
We pick up the ORDRSP from the vendors ftp-server and we would like to drop it to our backend system.
We can read the xml file into a string, but not send to the backend system, we use following steps:
- bytesToString
- stringToDocument
- documentToRecord
- recordToIDOC
- lockSession
- createTID
so far works perfekt
- sendIDoc
- releaseSession
On the step "sendIDoc" we see the described error message, but what is the message from the message?
Any Ideas?
Thank you and regards,
Michael

Hello Michal,
thank you for your quick answer!
In my opinion, i don't need any input for this service, because we pick up all data from the vendors ftp - server in a definied time interval.
All needed fields are available in the xml file. In the result tab is the IDocList filled correct, but no sending to the backend system because the error is displayed.
Is it a problem with my concept?
Regards,
Michael

Suggest EnhanceMent For SALES area determination In stock Transfer.

Suggest EnhanceMent For SALES area determination In stock Transfer.
V02V0001 Sales area determination for stock transport order Doesnt Work,

Is user exit required, as the sales area will be different. Incase of Intra company stock transfer the process will be as under:
Create Purchase Order (ME21N)
Create Delivery in background (VL04, VL10a, VL10C, etc)
Change Delivery for picking / packing & PGI (VL02n)
Create Billing Document (VF01)
Assumption: Stock Transfer configuration is in place. Assistance can be taken from SAP Best Practices in help.sap.com
Incase of Inter-company, the process will be as under:
Create Sales Order (VA01)
Create Delivery (VL01N, etc)
Change Delivery (VL02N)
Create Billing Document (VF01)
Assumption: Configuration is in place. Assistance can be taken from SAP Best Practices in help.sap.com
Regards,
Rajesh Banka

Standard IDOCS, Programs for posting FI & bank related data.

Hi,
(1)Are there any idocs available for posting FI documents, Vendor master?
(2)Are there any outbound idocs, programs for sending data to banks. EG:positive pay etc?
Kindly reply to these questions. Correct answer will be awarded points.
Regards,
Akshaya.

Hi,
There is message type BANK_CREATE for posting the FI related Bank details. Using the change pointers you can trigger the idocs for posting the bank related data.
Regards,
Uday

PAYEXT IDOC Enhancement for Japan

Similar Messages

Maybe you are looking for