URGENT:::::::::::::::::posting extended idoc
i have extended orders05...
created a purchase order and idoc was successully generated
. i've generated an inbound idoc using we19 tool.
my idoc shows status 51.. the error msg reads that there are entries to be made in required fields....
i've already changed the qualifiers too.
Hi,
Can you re-check the header part of the idoc, whether, the systems , message types, idoc type and the mandatory segments are there..................some time, the document will not posted for the same data.....
atleast you need to change some mandatory ones.
Thanks
Manju.
Similar Messages
-
Problem about extended IDOC(urgent)
Hi experts,
i have idoctype,extended idoc,and one include.. i need modify that according to the requirement.. here i will give the idoctype and extended idoc type and include program .. please help me where exactly i need to do the change and what are the steps required for the requirement..
Exact Requirement: Modify the program which populates the idoctype invoice02 and extension zinvoice02 , if netvalue is zero(vbrp-netwr = 0) then populate the idoc segment E1EDP01.E1EDP26 , BETRG WITH QUALF = # 011' WITH ZERO VALUE. curently segment is not populated.
Please help me in this and explain the steps required for this.
idoctype:invoice02
extended idoc:zinvoice02
include:ZXEDFU02
Here i am giving the include program
CASE dobject-kschl.
WHEN 'ZGRI' OR 'ZGDF' OR 'ZGRN' OR 'ZGAE'.
t_int_edidd[] = int_edidd[].
t_xtvbdpr[] = xtvbdpr[].
ta_xvbdkr = xvbdkr.
CASE int_edidd-segnam.
WHEN 'E1EDK01'.
ta_e1edk01 = int_edidd-sdata.
PERFORM get_shipment_data.
PERFORM get_route_data.
int_edidd[] = t_int_edidd[].
WHEN 'E1EDP01'.
Update segment E1EDP01
1. Update field E1EDP01-PSTYP
2. Accumulated net weight & quantity of batch split items against
E1EDP01 segment of the main invoice item.
ta_e1edp01 = int_edidd-sdata.
i_tabix = sy-tabix.
CLEAR: ta_e1edp02. "DIAG01+
PERFORM update_segment_e1edp01.
MOVE ta_e1edp01 TO t_int_edidd-sdata.
MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
Populate segment Z1EDP08
Fields: ZZDESPACTY_A, ZZACTYUOM
PERFORM validate_segment USING control_record_out-idoctp
control_record_out-cimtyp
'Z1EDP08'
CHANGING n_subrc.
CHECK n_subrc EQ 0.
PERFORM calc_invoice_item_zzdespacty_a. "DIAG02+
int_edidd[] = t_int_edidd[]. "DIAG02+
WHEN 'E1EDP02'. "DIAG01+
IF int_edidd-sdata(3) = '016'. "DIAG01+
ta_e1edp02 = int_edidd-sdata. "DIAG01+
ENDIF. "DIAG01+
WHEN 'E1EDP19'.
Populate segment Z1EDL24
Fields: Material Characteristics or Material Class '001'.
PERFORM validate_segment USING control_record_out-idoctp
control_record_out-cimtyp
'Z1EDL24'
CHANGING n_subrc.
IF n_subrc EQ 0.
ta_e1edp19 = int_edidd-sdata.
CASE ta_e1edp19-qualf.
WHEN '002'.
PERFORM get_mat_characteristic USING ta_e1edp19-idtnr.
PERFORM fill_segment_z1edl24.
int_edidd[] = t_int_edidd[].
WHEN OTHERS.
ENDCASE.
ENDIF.
WHEN 'E1EDP26'.
Populate segment E1EDP26
Fields: BETRG
i_tabix = sy-tabix.
ta_e1edp26 = int_edidd-sdata.
IF ta_e1edp26-qualf = '001'. "Gross Price which is always present
PERFORM fill_segment_e1edp26.
int_edidd[] = t_int_edidd[].
ENDIF.
WHEN 'E1EDP08'.
Populate Segment Z1EDL37 *
Fields: Bespoke fields from Handling Unit (VEKP)
PERFORM validate_segment USING control_record_out-idoctp
control_record_out-cimtyp
'Z1EDL37'
CHANGING n_subrc.
CHECK n_subrc EQ 0.
ta_e1edp08 = int_edidd-sdata.
PERFORM fill_segment_z1edl37.
Populate Segment Z1EDP08 *
Fields: Total Despatch Activity *
PERFORM validate_segment USING control_record_out-idoctp
control_record_out-cimtyp
'Z1EDP08'
CHANGING n_subrc.
CHECK n_subrc EQ 0.
PERFORM calc_invoice_item_acty_total.
int_edidd[] = t_int_edidd[].
WHEN OTHERS.
ENDCASE.
WHEN 'ZGDW'.
Line above added line below removed - Assyst 73789
WHEN 'ZGIN'.
t_int_edidd[] = int_edidd[].
t_xtvbdpr[] = xtvbdpr[].
ta_xvbdkr = xvbdkr.
CASE int_edidd-segnam.
Start SU02
WHEN 'E1EDK01'.
ta_e1edk01 = int_edidd-sdata.
i_tabix = sy-tabix.
Get the conversion factor
PERFORM modify_exchange_rate.
MOVE ta_e1edk01 TO t_int_edidd-sdata.
MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
int_edidd[] = t_int_edidd[].
End SU02
*************************************************************SAM01 START
WHEN 'E1EDP02'.
Populate segment Z1EDP02
Fields: Reason code for sales order
ta_e1edp02 = int_edidd-sdata.
CASE ta_e1edp02-qualf.
WHEN '002'.
PERFORM fill_segment_z1edp02.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDP02'
ta_z1edp02.
int_edidd[] = t_int_edidd[].
WHEN OTHERS.
ENDCASE.
***************************************************************SAM01 END
ENDCASE.
Start of JvdM01
WHEN 'ZGII'. "JvdM01
t_int_edidd[] = int_edidd[].
t_xtvbdpr[] = xtvbdpr[].
ta_xvbdkr = xvbdkr.
CASE int_edidd-segnam.
WHEN 'E1EDK01'.
Populate segment Z1EDKSH and Z1REM_STE_CDE
Fields: Shipment Number for Invoice
Reason code for sales order
ta_e1edk01 = int_edidd-sdata.
PERFORM fill_segment_z1edksh_ds.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDKSH'
ta_z1edksh.
PERFORM fill_segment_z1rem_ste_cde.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1REM_STE_CDE'
ta_z1rem_ste_cde.
int_edidd[] = t_int_edidd[].
WHEN 'E1EDKA1'.
Populate segment Z1EDKA1
Fields: Customer Account Group
ta_e1edka1 = int_edidd-sdata.
CASE ta_e1edka1-parvw.
WHEN 'RE'. "Bill To Party
PERFORM fill_segment_z1edka1.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDKA1'
ta_Z1EDKA1.
int_edidd[] = t_int_edidd[].
ENDCASE.
WHEN 'E1EDP01'.
Read segment E1EDP01 for use later "JVDM02
ta_e1edp01 = int_edidd-sdata.
WHEN 'E1EDP02'.
Populate segment Z1EDP02
Fields: Reason code for sales order
ta_e1edp02 = int_edidd-sdata.
CASE ta_e1edp02-qualf.
WHEN '002'.
PERFORM fill_segment_z1edp02.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDP02'
ta_z1edp02.
int_edidd[] = t_int_edidd[].
WHEN OTHERS.
ENDCASE.
WHEN 'E1EDP19'.
Populate segment Z1EDL24 and Z1EDP01 "JVDM02
Fields: Pack Size Activity for Material
Total Activity for Invoice Item
ta_e1edp19 = int_edidd-sdata.
CASE ta_e1edp19-qualf.
WHEN '002'.
PERFORM fill_segm_z1edl24_and_z1edp01.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDL24'
ta_z1edl24.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDP01'
ta_z1edp01.
int_edidd[] = t_int_edidd[].
WHEN OTHERS.
ENDCASE.
ENDCASE.
End JvdM01
ENDCASE.
Start SU02 Code Comment for implementing IR 340
**mpc01 - start of insert
start assyst 73789
*IF dobject-kschl = 'ZGDW'."amersham invoices
**IF dobject-kschl = 'ZGIN'."amersham invoices
end assyst 73789
CASE int_edidd-segnam.
for the organisation data header
WHEN 'E1EDK14'.
MOVE int_edidd-sdata TO ta_e2edk14.
where is qualifying organisation = 003 (delivering company code).
IF ta_e2edk14-qualf = '003' AND ta_e2edk14-orgid NE space.
SELECT SINGLE waers
INTO t001-waers
FROM t001
WHERE bukrs = ta_e2edk14-orgid.
IF sy-subrc = 0.
t_int_edidd[] = int_edidd[].
get the billing date for the invoice
LOOP AT t_int_edidd WHERE segnam = 'E1EDK02'.
MOVE t_int_edidd-sdata TO ta_e1edk02.
IF ta_e1edk02-qualf = '009'."billing date
w_fkdat = ta_e1edk02-datum.
EXIT.
ENDIF.
ENDLOOP.
if no invoice date use current date
IF w_fkdat IS INITIAL.
w_fkdat = sy-datum.
ENDIF.
change the general document header
LOOP AT t_int_edidd WHERE segnam = 'E1EDK01'.
i_tabix = sy-tabix.
MOVE t_int_edidd-sdata TO ta_e1edk01.
set the field to the default currency code for the company
ta_e1edk01-hwaer = t001-waers.
if the default value equals the idoc currency then exit
IF t001-waers = ta_e1edk01-curcy.
EXIT.
ENDIF.
get the exchange rates
SELECT *
INTO TABLE t_tcurr
FROM tcurr
WHERE kurst = 'NYB1' " SU01
WHERE KURST = 'GEBU' " SU01
AND fcurr = ta_e1edk01-curcy
AND tcurr = t001-waers.
IF sy-subrc NE 0."no values found
error the idoc
MESSAGE e400(vf) WITH c_exchange_rate_error
RAISING error_message_received.
EXIT.
ENDIF.
LOOP AT t_tcurr.
convert to date from inverted date to normal date format.
CALL FUNCTION 'CONVERSION_EXIT_INVDT_OUTPUT'
EXPORTING
input = t_tcurr-gdatu
IMPORTING
output = w_datum.
CONCATENATE w_datum+6(4)
w_datum+3(2)
w_datum(2)
INTO t_tcurr-datum.
MODIFY t_tcurr.
ENDLOOP.
sort the exchange rates with the newest first.
SORT t_tcurr BY datum DESCENDING.
read the first value in the table ie the newest.
LOOP AT t_tcurr WHERE datum <= w_fkdat.
EXIT.
ENDLOOP.
IF sy-subrc NE 0."no values found
error the idoc
MESSAGE e400(vf) WITH c_exchange_rate_error
RAISING error_message_received.
EXIT.
ENDIF.
Start SU01
Get the Exchange rate from the function module and populate
E1EDK01 TABLE
w_fcurr = ta_e1edk01-curcy.
call function 'CONVERT_TO_LOCAL_CURRENCY'
exporting
date = w_fkdat
foreign_amount = '0'
foreign_currency = w_fcurr
local_currency = t001-waers
type_of_rate = 'GEBU'
importing
exchange_rate = t_tcurr-ukurs
exceptions
no_rate_found = 1
overflow = 2
no_factors_found = 3
no_spread_found = 4
derived_2_times = 5
others = 6.
End SU01
ta_e1edk01-wkurs = t_tcurr-ukurs.
change the header data in segment
MOVE ta_e1edk01 TO t_int_edidd-sdata.
update the current idoc segment
MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
EXIT.
ENDLOOP.
update all of the idoc segments
int_edidd[] = t_int_edidd[].
ENDIF.
ENDIF.
ENDCASE.
*ENDIF.
**mpc01 - end of insert
End SU02 Code Comment for implementing IR 340Hi Venu,
Try with this code.
If vbrp-netwr = 0.
<b> WHEN 'E1EDP26.
CASE ta_e1edp26-qualf.
ta_e1edp26 = int_edidd-sdata.
WHEN '011'.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'e1edp26'
ta_e1edp26.
int_edidd[] = t_int_edidd[].
ENDCASE.</b>
ENDIF.
Thanks
Manju. -
Hi all,
I want to extend idoc MBGMCR03 to pass serial no. data since the client serial no. length is 40 chars whereas SAP supports only 18 chars. When I try to extend the idoc, I get error message 'Action is not possible for generated idoc types'.
This idoc being a ALE-BAPI interface cannot be extended.
Can anyone tell me what's the best way of passing the serial no. data through the idoc? I have thought of using segment E1BPPAREX as nothing is being passed in it. We will be having a custom process code function module in which the values will be stored in an internal table and then the fields will be cleared so that the idoc can be posted.
Thanks,
ShomaHi Gordon,
Cann't i extend the MBGMCR03 Idoc type .I need to add 2 fields MENGE and ELIKZ.
Do we need to have primary key field in WE31 along with MENGE and ELIKZ like Item no EBELP.
I created a structure with above 4 fields along with EBELN.
I am not able to create extension in WE30.
it is saying that " Action is not possible for generated idoc types".
Please let me know the User exit or Customer Exit to use to populate the data.
Please help
Thanks & regards
Vishnu
Edited by: vishnukvv on Mar 4, 2011 11:57 AM
Edited by: vishnukvv on Mar 4, 2011 12:08 PM
Edited by: vishnukvv on Mar 4, 2011 12:10 PM
Edited by: vishnukvv on Mar 4, 2011 12:27 PM
Edited by: vishnukvv on Mar 4, 2011 12:28 PM -
for extended idoc i added the extended segment to basic type and doen
the code as per that but i would like to confirm one thing that for
every extended idoc for process code we need to modify the existing FM
like MASTERIDOC_CREATE_DEBMAS ,
for this FM we need to finc the enhansment and then modify the code
as per that , so is the same for all extended idoc we need to find
related FM for that and find enhancement and modify .Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
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.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
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. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
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.
regards,
srinivas -
Hi,
I have extended inbound idoc and added segment.. i m using standard function "IDOC_INPUT_FIDCC2" for posting through idoc (FB70)..
now i want to do coding for the newly added segment.. however i m not getting customer exit where enhancement spot can be created for the logic...
i want to use function "SAVE_TEXT" in the customer exit.. so mainly once document is generated i can add FI note by using function "SAVE_TEXT"..
Please let me know which way i can achieve this (name of user exit ??)
Regards,Hi Santosh,
If you don;t have User EXit then copy FM IDOC_INPUT_FIDCC2" into 'Z' FM and write your code and define 'Z' FM into WE20 T-code. -
Error while posting the IDoc for Customer Invoice.
hi,
I m posting Customer Invoice through LSMW using IDocs.
Basic type is FIDCCP02 and message is FIDCC2.
While posting the Idoc I m getting error as:
'Document or line item does not exist for invoice reference'.
I m not getting the error why it is asking for invoice reference because
in FB01 it is not asking for any reference or anything.
Even in f-22 also it is not asking for the same.
In Idoc all the item level values are coming prorperly.
If anybody worked on such issues then please reply.
-Thanx.
-UmeshHi,
Where you able to resolve your issue, I would appreciate if you can share the solution.
Thanks -
Error while posting Invoice IDOC (The difference is too large for clearing)
Hi All,
While posting Invoice IDOC to Remittance Advice IDOC get fails with status 51 & message ' The difference is too large for clearing'.
Please suggest any solution or reason to fail IDOC.
Thanks & Regards,
Ajay
Moderator message: please search for information and try to find out yourself before asking, this will be a functional problem anyway that should be asked in the appropriate forum, e.g. ERP Financials.
locked by: Thomas Zloch on Aug 20, 2010 1:59 PMPls check the tolerance amounts limits:
SPRO--- F/A --AR/AP -
Business transactions -Open item clearing--- Clearing differance---- Define / Assign tolerance groups for emp -
Where you need to change the limits of max amounts with the %
Let me know for any info.
Regards
Suresh -
Non-po invoice posting using IDOC into LIV module
Hi,
does anyone know if idoc interface is available for posting non-po invoice as an LIV invoice into MM module. what I found that I can post the idoc to FI module directly using message code - FI.
Thanks.Hi
I Got your name from this site.I would be very thankful if you can help me here.I am designing a EDI based invoice LIV.Is it possible to post some charges which are without PO reference but are coming in Vendor Invoices.Is it possible to post these kind of charges with EDI message INOIC01 or we have to post through FI posting.If possible through EDI in which segment of IDOC we will enter these charges with amt.Also is it possible to post credit memo also with EDI
Thanks
Sanjeev -
Error while trying to post inbound idoc of message type COND_A
Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
MohitI do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated. -
Error while posting the IDOC. Status message '56'
Hi,
I have a requirement where I will post an IDOC which inturn will split the original IDOC into child IDOCs based on the store value.
I am trying to post the IDOC in WE19. So, the Original IDOC is posted successfully with status '53'. Whereas, the child IDOCS finished with error. The status of the message is '56' and the error says 'EDI: Partner profile not available'. Could someone tell me what could be the reason for this..?
Actually, the IDOC was created by the Functional Consultant. So, should the partner profile creation also done by them or do we need to do anything to solve this problem.? Could someone answer me this question. Thanks in advance.
Best Regards,
Paddu.It looks like the control data for the child segment is not getting populated. you have to find the code which populated the control data and see if it is doing what it should.
-
Error while posting the Idoc 'Update error, transaction VA01'
Hi Gurus,
When an inbound Idoc for sales order is trying to post we are getting the error 'Update error, transaction VA01'.
Aslo following are the details of the error:
Update error, transaction VA01
Message no. 00377
Diagnosis
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA01.
Update information
Return code: 009
Text : Error during insert table FPLTC (RC= 1, Key= )
Procedure
Pleas analyse your Batch-Input data.
You can also examine your posting data using the transaction SM13.
Can somebody let me know what would be the cause.
Also the we are trying to post the Idoc with a Id which is having maximum Authorization.Hi,
Where you able to resolve your issue, I would appreciate if you can share the solution.
Thanks -
Error while posting Shipment IDOC
Hi..
I have an inbound IDOC TPSSHT01, which has been extended by adding a Z segment.. But I keep getting an error message.. The IDOC is created with status 56 and the message says "No inbound profile found".. I have configured the Inbound profile to include the message type in wWE20 and also added the message type in WE57 and WE82... Do i need to do any further settings?
RishiHmm.. I don't think anything else is required for the inbound. Take a look at the control record of your IDoc - maybe it's not looking for the profile that you've set up in WE20. Partner # / type / message code must match.
Also make sure that in WE57/82 you have the standard IDoc type and your Z... extended IDoc type. -
How to find out the inbound function module in the extended idoc
Hi,
how to find out the inbound function module in the extended idocs
Thanks .through we41/we42 you can find the inbound function module.......
or
thorough we19(idoc test tool) ....
give the input as message type or basic idoc..
press exec...
then you can find th button on application tool bar as inbound funtion module....
from here also you can find..........
<REMOVED BY MODERATOR>
Khasimsa
Edited by: Alvaro Tejada Galindo on Apr 14, 2008 1:34 PM -
Creation of New Message Type for Extended IDoc
Dear Friends,
I want to create New Message Type for MATMAS and want to Active Change Pointers accordingly. Thru this Message Type how can I able to use Extended IDoc which I have created for Basic Idoc Type MATMAS05.
I am Sending Data from SAP to XI ; Any one can help me in this How can I create the Message Type with the IDoc Extn .
for Change Pointers.
Warm Regards,
Naveen Mutyapu.Hi naveen mutyapu,
see these links
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
http://www.allinterview.com/rss/interview-questions/new/SAP-ALE-IDocs.xml
happy learning.
thanks
karthik -
Not able to Post multiple IDOCS
Hi All,
I am getting my output from XSLT mapping like below:
<?xml version="1.0" encoding="UTF-8" ?>
<ZORDERS5>
+ <IDOC BEGIN="1">
+ <IDOC BEGIN="1">
</ZORDERS5>
But in the SAP R/3 it is able to post only the last IDOC (which is second IDOC in this case). I want to post all the IDOCS. What could be the problem?
Edited by: sreinivas prak on May 13, 2008 11:12 AMHi Srinivas,
Post multiple IDOCS
There are two Message Mappings involved in the whole scenario. First mapping is N:1 Mapping which will be used in BPM and second Mapping is 1:1 Mapping:
1. First Message Mapping  N: 1 Mapping between IDoc (occurrence 0...unbounded in Messages tab) to IDoc with changed occurrence of its top node (IDOC) as 0...unbounded.
Check these Blogs:
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter
/people/prasadbabu.nemalikanti3/blog/2006/02/24/collecting-and-bundling-vendor-records-from-different-multiple-interfaces-file-systempeoplesoft-and-sending-to-sap-r3-system-part-1
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on May 13, 2008 11:21 AM
Maybe you are looking for
-
How to link a value in a cell to a page number?
I have a series of diagrams that I'd like to create a table for showing the page it's on, and a description of it. during creation, i an simply store the value of the page number in an array, and use it when creating the table, however, if the diagra
-
SQL Developer in Read-Only-Mode
Oracle SQL Developer version 1.2.1 BUILD MAIN-32.13 Running under WinXP Issue description: Impossible to start SQL Developer in Read-Only-Mode for certain users who should not be able to modify any data.
-
For the last 6 months my powermac has been on the carpet under my desk rather than on my desk to save space. Installing the airport card the other day, I noticed how much "fluff" build up there is now from the carpet. Any suggestions for cleaning it?
-
Hello, I recently installed ArchLinux on my desktop computer. My desktop computer has two Radeon 7950s and an i7-2600 inside of it. I also installed Xorg and XFCE4. However, I am having a problem. My graphics performance is dreadfull. Minecraft runs
-
Is there a way to remove audio clipping w/in FCE? I shot some live video of a local band, but audio isn't usable.