IDOC customer fields

Hi,
I am currently using the IDOC BUPAFS_FS_CREATE_FRM_DATA which creates a business partner.
We have used the easy enhancement workbench to add new fields to the Business Partner.
I am wondering if it is possible to add these fields to the existing IDOC so we can use it to bring through the extra data.
I have tried creating a extension, but get the error "Action not possible for generated IDOCS"
Thanks
James

Hi James,
Refer the following link.
[http://help.sap.com/saphelp_sm40/helpdata/en/6c/764715ab2a4c2a8421429d17d8ac2c/frameset.htm]
It may be of help to you.
Thanks,
Surya

Similar Messages

IDOC Custom Fields are not coming in MII

Hi Guys,
I am receiving Standard IDOC (MATMAS) with Custom segment. Custom segment having two Z-fields and One Standard field. While fetching the IDOC at MII end, I am able receive IDOC except Z-fields, Custom Segment is coming perfectly with the one Standard field but missing Zfields.
I'm using MII 12.1.5 Build(92). Please provide your suggestions on this issue.
Thanks!

Check if your MII is capbale of reciving the custom fileds. check mapping on sender and reciver side if z fileds are mapped correctly.
Check and evert,
Santosh Sarda

LSMW : Idoc method , Business Activities custom fields data upload

Hi guys
I am uploading Business activities using LSMW IDOC method and below message and idoc type
Message type CRMXIF_ORDER_SAVE_M
Basic idoc type : CRMXIF_ORDER_SAVE_M02
Using EEWB I added few fields to business activities , along with the standard fields I want to upload the customer fields also .
I tried to Extend the Basic idoc type CRMXIF_ORDER_SAVE_M02, but it was not allowing me to Extend ( since it is generated basic idoc type ) I tried the other Basic idoc types for Business activities , I got the same problem
the basic idoc type contains only two Segments
E101CRMXIF_CUSTOMER_H_X (parent)
E101CRMXIF_CUSTOMER_H (child)
with out my custom fields
pls help how can i add my custom fields ( added by eewb) to the basic idoc type
for uploading custom fields
thanks in advance
Warm regards
Rajasekhar

You are going to need to create an enhancement of the standard IDOC type in order to get your custom fields to show. I can't remember the exact procedure, but you will need to create a Z-type based on the existing type in the system. When you generate the z-type the fields will be filled in.
Look at the following thread and it will give the basic steps
How to delete Extention
Good luck,
Stephen

Custom fields in ORDERS05 Idoc

Hi Guys,
For our scenario we have extended the custom IDOC ORDERS05 to add one custom field (ZZREF) in the header and one at the line item level (ZZLINEREF).
Same fields have been appended to VBAK (Order header) and VBAP (Line items) tables.
Now the problem is I am unable to find a standard way of populating these standard tables with the values coming in the custom fields.
I am using standard process code attached to function module IDOC_INPUT_ORDERS. this function module creates the order using call transaction method, which is creating a problem to pass on the values.
Can you please help me on this situation and provide me with the possible solutions.
Thanks
Sandeep

Hi Sandeep,
U can copy ur Statndard FM IDOC_INPUT_ORDERS to ZFM and ( fill those two fields ) assign to newprocess code.
And replace the old processcode with newprocesscode.
I hope this will resolves your problem.
Regards,
Venkat.

Sending idocs for custom field

Hi
I need to send idocs when i save the data in field , the idocs should be send automatically when the data saved to field, please provide the solution.
Thanks
Moderator message: "spec dumping", please work yourself first on your requirement.
Edited by: Thomas Zloch on Jun 23, 2011 9:17 AM

Hi
In case you have created a structure for your custom fields and added it to the standard table then you would be looking for a user exit so that the data entered in those fields from the MM01 or MM02 screen gets stored into the database.
Over there you can trigger a custom event and start your approval workflow.
If the approval is given then set a parameter say Approval as X in the workflow.
Read the workflow container in your exit for this container element and if its value is X,then move the corresponding data to the desired structure or else clear it.
Lets say you have added fields in CJ01 and it has two exits for storing the data in database.PROJ is the table and custom fields added in CI_PROJ
EXIT_SAPLCJWB_002
move-corresponding sap_proj_imp to proj.
EXIT_SAPLCJWB_003 :
call F.M. swe_event create
wait for say a particular time limit after which it should be considered as auto rejected read workflow container for this approval value
if X
move-corresponding proj to cnci_proj_exp.
else.
fire another event to cancel the workflow.
endif.
I am not sure this would be an appropriate way but could be tried.

Sending custom field added in Standard infotype through idoc

Hello All,
We have a requirement where custom field of a standard infotype 0002 needs to be sent through idoc only to a desired destination system.
My Approach:
I have created a custom segment having custom field from IT 0002 & mapped this segment in T777D table.
But the problem with above, is all the system who are receiving IT0002 will be receiving this custom segment also including desired system.
How can it be filtered?

Hi,
Create the new segment and message types of the idoc with cutom field.
Then map the new mesage type and corresponding receiver( SM59).

Sending custom field added in Standard table through idoc

Hello Folks,
We have a requirement where custom field of a standard table PA0002 needs to be sent through idoc only to a desired destination system.
My Approach:
I have created a custom segment having custom field from PA0002 & mapped this segment in T777D table.
But the problem with above, is all the system who are receiving PA0002 will be receiving this custom segment also including desired system.
How can it be filtered?

Hi,
In BD64 you can do the segment level filtering. Go to BD64, search for your distribution model there drill down to "filter settings" the make the required segment filtering.
Thanks,
Asit Purbey.

Idoc extension for eewb custom fields for BUS20001

Hello.
I have an almost exact question as , but I still need to ask what I'm supposed to do.
We've done enhancements in EEW and I can see some append structures in CRMXIF_BUSTRANS (for example). The problem is that when I generate outbound idoc the sturcture E101CRMXIF_BUSTRANS is missing the corresponding append structures.
Why isn't EEW adding this, or do I have to generate/re-generate something?
I've tried to Cancel release/release the ALE interface in BDFG, but with no results.
I think the replications (initial load and delta load) to r/3 has all EEW modifications, but when it comes to idocs, it woun't change.
Is the only solution to create a new idoc in bdfg and create a z-structure?
The FM ALE_CRMXIF_ORDER_SAVE_M used for populating the idoc, would work if the structure E101CRMXIF_BUSTRANS was extended with the same appendstructure (since the only thing it does is a move-corresponding...).
So, the question is if I have to create a new z-idoc, or if it's possible to regenerate the structure used in the idoc segments?
Regards, Mikael Löwgren

Hi,
When you have ignored the inconsistencies, this means the complex structure fields and the corresponding Idoc Segment fields are different in the support package.
If this is the case, when the Idoc is regenerated in Tx BDFG, you will find the message type will be in
error when you press F9 to do the syntax check.
There you will see the segments which are in error as well as the 'Interface is not current and it must be regenerated' error message.
Check those segments listed in syntax check against the respective complex structure. If there are differences like if some fields are added or the data element is changed, kindly correct the segment fields via Tx IDOC.
If you need to add fields to the segment, you need to increase the field length of the segment in EDISDEF table, which can be done in Tx IDOC --> Repair segments tab --> Change entries in EDISDEF table.
There you can change the field length and then change the entries in EDSAPPL table.
Similarly if you take out all the errors in the segments listed for a particular message type and try to release the Idoc, it will be released without any errors.
This happens, as far as my understanding goes, mainly because the complex structures might under go some changes from the development side but not the Idocs. Since both are different entities, mostly these types of things happen.
Do let me know if this has helped you.
Venkat

How to populate a custom field of a Std. SAP Tx with BAPI usage 2 Load data

Hi Experts,
For instance, I created a custom field (say, custom_field_1) on a screen of standard SAP tx(say, ME21N) by using screen exit. And in order to populate the data into it (custom_field_1), will use the Function user exits of this Tx(ME23N).
1) In next step, Where Where I have to add this field, apart from appending the same custom field in EKKO/EKPO table or any other related table; Extending the corresponding IDOC or creating a new Custom ÍDOC type? like What about BAPI?
2) If I got a text file with the data (including the data for this custom_field_1 too) and I have been asked to load it into SAP, then, I decided to use BAPI (say, BAPI_PO_CREATE or CREATE1) to create the data, So, How to handle this custom field, I mean, In which BAPI structure I have to pass this custom_field_1 data? ( Iguess, for some BAPIs EXTENSIONIN structures are provided, sorry if am wrong!)
Thank you.
Edited by: SAP ABAPer on Feb 21, 2009 7:40 PM

for example if you added field in the VBAP table then you can pass the custome field values like below
     move 'BAPE_VBAP' to lwa_extension-structure.
      lwa_bape_vbap-vbeln = lwa_final-vbeln.
      lwa_bape_vbap-posnr = lv_posnr.
      move lwa_final-yyslotid to lwa_bape_vbap-new custome field.
      move lwa_bape_vbap to lwa_extension-valuepart1.
      append lwa_extension to lt_extension.
      clear lwa_extension.
      move 'BAPE_VBAPX' to lwa_extension-structure.
      lwa_bape_vbapx-vbeln = lwa_final-vbeln.
      lwa_bape_vbapx-posnr = lv_posnr.
      move 'X' to lwa_bape_vbapx--new custome field.
      move lwa_bape_vbapx to lwa_extension-valuepart1.
      append lwa_extension to lt_extension.
      clear lwa_extension.
call function 'BAPI_SALESORDER_CHANGE'
        exporting
          salesdocument    = strcture
          order_header_inx = strcture
        tables
          order_item_in    =strcture
          order_item_inx   = strcture
          schedule_lines   = strcture
          schedule_linesx = strcture
          extensionin      = lt_extension.

Custom fields not getting updated in Mass Maintenance-MM17

Hi,
I have created a custom field in MARC table and the data is getting updated to the MARC table through MM01/MM02 but it is not getting updated by MM17. I have checked the notes 44410, 576160, 414020 and 116311. I have done the following changes as per the sap notes.
1. Created a custom segment ZE1MARCM by copying the standard segment E1MARCM and added the custom field in that
    segment.
2. I have extended the IDOC 'MATMAS03' and added the custom segment ZE1MARCM to E1MARAM.
3. Created a new entry in we82 and provided the extension type 'ZMATMAS03' and release '701'.
4. Adjusted the partner profile in we20 for matmas with port and providing the extension idoc type.
5. Added the custom field in the table MASSFLDLST.
6. Implemented the code in BADI 'MG_MASS_NEWSEG' and exits 'EXIT_SAPLMV01_002' , 'EXIT_SAPLMV02_002' as per the
    sap notes.
The custom field is not getting updated through mass maintenance. Please let me know if i have missed anything?
Thanks,
Geeta

I had this same question several years ago. Please check my answer at Initialize MARC Custom Fields Using MM17 Does Not Work

Custom Fields from SRM 7.0 to R/3 4.7

Hi,
I have some custom field which need to be passed from the SRM confimation to R/3 - GR, I learnt that Idoc MBGMCR01 is triggered to create the GR in R/3.
1. Wether I have to create a new IDOC type and assign in the message type? Please let me know in which BADI i can populate the value for the custom Fields
Edited by: prabhu jayaraman on Oct 5, 2009 3:38 AM

Hello Prabhu,
You need not create a new idoc. You can extend the existing Idoc using extensions.
However in the related FM BBP_ALE_GOODSMVT_CREATE which triggers the Idoc , i do not see any BADI being called.
Best Regards,
Pavan
Edited by: pavancv on Nov 18, 2009 4:13 PM

Custom Fields in BP to be replicated to KNA1

Hi.
I am working on the SAP CRM 4.0 and SAP r/3 4.6C.
I have extended the BP by custom fields by EEWB and also the KNA1 table in R/3.
ZBSTC000000000C is the structure in the BUT000 with the field ZZSHIPTOSTOR0001.
ZBSTC000000000C is also added in KNA1 table with the field ZZSHIPTOSTOR0001.
We would be creating the BP's in the CRM and have them delta downloaded to R/3.
The data in the field ZZSHIPTOSTOR0001 should also be replicated to the R/3.
IN CRM.
I have created the FM : Z_BANK_MASTER_SMOUTIL2 in the CRM and made entry in the table TPS34 for the Procss SMOUTIL2.
The Code is as below.
FUNCTION Z_BANK_MASTER_SMOUTIL2.
""Local interface:
*" IMPORTING
*" VALUE(I_HEADER) TYPE SMW3_FHD
*" VALUE(I_TRANSACTION_HEADER) TYPE SMO8_TMSG
*" VALUE(I_TRANSACTION_MESSAGE) TYPE ANY
*" VALUE(I_MESSAGE_EXT) TYPE ANY
*" VALUE(I_SITE_ID) TYPE SMOG_SITE
*" REFERENCE(I_RECIPIENTS) TYPE SMW_RECTA2
*" REFERENCE(I_QNAME) TYPE TRFCQNAM
*" TABLES
*" T_BAPIMTCS STRUCTURE BAPIMTCS
*" T_BAPICRMSFK STRUCTURE BAPICRMSFK
*" T_BAPIPAREX STRUCTURE BAPIPAREX
*" TI_QRFCRCV STRUCTURE QRFCRCV
*" CHANGING
*" REFERENCE(E_STATUS) TYPE SMW3_RECST
*" REFERENCE(E_SUCCESS_BEHAVIOUR) TYPE SMOFSUCBEF
*" REFERENCE(E_NO_STANDARD_UPLOAD) TYPE XFELD
*" REFERENCE(ERROR_SEGMENTS) TYPE SMW_ERRTAB
*" REFERENCE(E_BAPICRMUH1) TYPE BAPICRMUH1
data : ls_ZZSHIPTOSTOR0001 type ZILGCUSTOMFIELDS.
data : ls_bapimtcs TYPE bapimtcs,
 lv_partner_guid TYPE bu_partner_guid_32,
 next_free_currdno TYPE currdno VALUE 1.
CASE i_header-bdoc_type.
Extension for Business Transaction
 WHEN 'SALESDOCUMENT'.
Extension for Business Partner
 WHEN 'BUPA_MAIN'.
 CALL FUNCTION 'Z_MAP_BUPA_TO_MW'
 EXPORTING
 i_header = i_header
 i_transaction_header = i_transaction_header
 i_transaction_message = i_transaction_message
 i_message_ext = i_message_ext
 i_site_id = i_site_id
 i_recipients = i_recipients
 TABLES
 t_bapimtcs = t_bapimtcs
 t_bapicrmsfk = t_bapicrmsfk
 t_bapiparex = t_bapiparex
 CHANGING
 e_status = e_status
 e_success_behaviour = e_success_behaviour
 e_no_standard_upload = e_no_standard_upload
 error_segments = error_segments
 e_bapicrmuh1 = e_bapicrmuh1.
ENDCASE.
*Use the following macro definition to get full Unicode support:
Macro MOVE_CASTING *************************************
FIELD-SYMBOLS: <unicode_x1> TYPE x,
<unicode_x2> TYPE x.
DEFINE move_casting.
 assign &1 to <unicode_x1> casting.
 assign &2 to <unicode_x2> casting.
 move <unicode_x1> to <unicode_x2>.
END-OF-DEFINITION.
ENDFUNCTION.
FUNCTION Z_MAP_BUPA_TO_MW.
""Local interface:
*" IMPORTING
*" REFERENCE(I_HEADER) TYPE SMW3_FHD
*" REFERENCE(I_TRANSACTION_HEADER) TYPE SMO8_TMSG
*" REFERENCE(I_TRANSACTION_MESSAGE) TYPE ANY
*" REFERENCE(I_MESSAGE_EXT) TYPE ANY
*" REFERENCE(I_SITE_ID) TYPE SMOG_SITE
*" REFERENCE(I_RECIPIENTS) TYPE SMW_RECTA2
*" TABLES
*" T_BAPIMTCS STRUCTURE BAPIMTCS
*" T_BAPICRMSFK STRUCTURE BAPICRMSFK
*" T_BAPIPAREX STRUCTURE BAPIPAREX
*" CHANGING
*" REFERENCE(E_STATUS) TYPE SMW3_RECST
*" REFERENCE(E_SUCCESS_BEHAVIOUR) TYPE SMOFSUCBEF
*" REFERENCE(E_NO_STANDARD_UPLOAD) TYPE XFELD
*" REFERENCE(ERROR_SEGMENTS) TYPE SMW_ERRTAB
*" REFERENCE(E_BAPICRMUH1) TYPE BAPICRMUH1
tables : bnka,but000.
data : int type i.
data : ls_ZZSHIPTOSTOR0001 type ZILGCUSTOMFIELDS.
data : ls_ZBSTC000000000C type ZBSTC000000000C.
data : ls_ZILGCUSTOMFIELDS type ZILGCUSTOMFIELDS.
data : ls_bapimtcs TYPE bapimtcs,
 lv_partner_guid TYPE bu_partner_guid_32,
 next_free_currdno TYPE currdno VALUE 1.
data : ls_but000 type but000.
FIELD-SYMBOLS: <fs_msg_bupa> TYPE bus_ei_main,
<fs_msg_bpext> TYPE bus_ei_extern.
DATA lr_cast_illegal TYPE REF TO cx_sy_assign_cast_illegal_cast.
DATA lr_cast_unknown TYPE REF TO cx_sy_assign_cast_unknown_type.
DATA : LS_BNKA TYPE BNKA,
 LS_BNKA_MEM TYPE BNKA,
 LT_BNKA TYPE TABLE OF BNKA,
 LT_BNITAB TYPE TABLE OF BNKT,
 UNAME LIKE SY-UNAME.
DATA: BEGIN OF PARAMETER_TAB OCCURS 0.
 INCLUDE STRUCTURE ZPARAMETER.
DATA: END OF PARAMETER_TAB.
loop at T_BAPIMTCS.
 if T_BAPIMTCS-currdno > next_free_currdno.
 next_free_currdno = T_BAPIMTCS-currdno + 1.
 endif.
endloop.
assign i_message_ext to <fs_msg_bupa>.
if sy-subrc <> 0.
 exit.
endif.
LOOP AT <fs_msg_bupa>-partners
ASSIGNING <fs_msg_bpext> WHERE header-object_instance-bpartnerguid EQ T_BAPIMTCS-OBJKEY.
 select single * from But000 where PARTNER_GUID eq T_BAPIMTCS-OBJKEY.
pack data into transfer structure
 CLEAR: ls_bapimtcs.
 ls_bapimtcs-tabname = 'ZBSTC000000000C'.
 ls_bapimtcs-segtype = 'DA'.
 ls_bapimtcs-currdno = next_free_currdno.
 ls_bapimtcs-objkey = lv_partner_guid.
 ls_bapimtcs-relkey = lv_partner_guid.
 move-corresponding But000 to ls_ZBSTC000000000C.
 move_casting ls_ZBSTC000000000C ls_bapimtcs-data.
 APPEND ls_bapimtcs TO t_bapimtcs.
ENDLOOP.
ENDFUNCTION.
The table t_bapimtcs is populated with the structure ZBSTC000000000C.The data is also populated.
IN R/3 system.
I have created the FM "ZSAMPLE_PROCESS_CRM0_300".
The table TPS34 is added with CRM0_300 as procs and the FM "ZSAMPLE_PROCESS_CRM0_300" is assigned.
FUNCTION ZSAMPLE_PROCESS_CRM0_300.
""Local interface:
*" IMPORTING
*" REFERENCE(I_BAPICRMUH1) LIKE BAPICRMUH1 STRUCTURE BAPICRMUH1
*" EXPORTING
*" REFERENCE(E_NO_STANDARD_UPLOAD) LIKE CRM_PARA-XFELD
*" TABLES
*" T_BAPIMTCS STRUCTURE BAPIMTCS
*" T_BAPIPAREX STRUCTURE BAPIPAREX
*" T_BAPICRMSFK STRUCTURE BAPICRMSFK
*" T_BAPICRMMSG STRUCTURE BAPICRMMSG
*" EXCEPTIONS
*" EVENT_NOT_CALLED
data : int type i.
data : c_kunnar like kna1-kunnr.
data : o_kna1 like standard table of kna1,
 n_kna1 like standard table of kna1,
 I_KNA1 like standard table of kna1,
 i_knb1 like standard table of knb1.
data : o_but000 like standard table of but000,
 n_but000 like standard table of but000.
tables : kna1.
data : ls_ZBSTC000000000C type ZBSTC000000000C.
data : ls_ZZSHIPTOSTOR0001 like kna1-ZZSHIPTOSTOR0001.
case I_BAPICRMUH1-OBJNAME.
 when 'CUSTOMER_MAIN' OR 'BUPA_MAIN'.
endcase.
field-symbols : <fs_msg_kna1> type kna1,
 <fs_msg_cuext> type ZBSTC000000000C.
data : g_kunnr like kna1-kunnr.
loop at T_BAPIMTCS where tabname eq 'BSC_MAINI'.
 move t_bapimtcs-data+0(10) to g_kunnr.
endloop.
loop at T_BAPIMTCS where tabname = 'ZBSTC000000000C'.
 move_casting t_bapimtcs-data ls_ZZSHIPTOSTOR0001.
endloop.
field-symbols : <unicode_x1> type x,
 <unicode_x2> type x.
define move_casting.
 assign &1 to <unicode_x1>casting.
 assign &2 to <unicode_x2>casting.
 move <unicode_x1> to <unicode_x2>.
end-of-definition.
ENDFUNCTION.
The table t_bapimtcs is populated with the data.
But i am not able to have the data in the table KNA1 table of the R/3 system.
How can i unpack the data in t_bapimtcs and modify the table KNA1.
Could any one pls advise.
Thanks.
Muraghendra D

Hello Muraghendra, I had a very similar requirement in my project and ran in to similar problems. The idea of packing data on the CRM side and unpacking on the R/3 side was relatively straight forward, but how to update KNA1 or KNVV in my particular case, was a bit tricky. It turned out that one needs to manipulate an IDOC. In our correspondence with SAP on the matter they said the following:
+"In R/3 the processing(in both cases replication and updation) is done in the following manner.
1.The BAPIMTCS structures are converted to complex structures.
2.The complex structures are converted to Idocs.
3.The checks for required fields is made.
4.The data is saved to the data base via a batch input transaction.
Note: Unlike in CRM, R/3 does not use BAPIs for saving to data base.
The function module PI_BP_DE_BALE_VTBER in the R/3 system(this is present in the UD1 system) can be used as a template for converting the BAPIMTCS to complex structure and to Idocs. Once the data is present in
the Idocs, the batch input would take care of saving the data. The flow would be the same in both the cases (replication and updation).
You may register your function module with the event DE_BALE. This function module would be called just before the system executes Step 3.
Note: The Idocs that are used are mapped directly to the underlying tables table(for example KNA1, KNVV etc.) and will have the necessary field(in this case KNVV-PERFK)."+
In my particular example I had to enhance the business partner on the CRM side with the field PERFK. This field already exist on the R/3 side and the task was then to allow CRM to be the master of all customer updates and consequently transfer any changes of the field PERFK in CRM to KNVV-PERFK in R/3. I think you will find that this requirement is similar to your own requirement.
In the end my code looked like this in R/3:
DATA: LV_FOUND TYPE C,
 LS_E1KNVVM LIKE E1KNVVM,
 LS_E1KNA1M LIKE E1KNA1M,
 LS_IDOC_DATA LIKE EDIDD,
 LS_PERFK type BSS_CENTI.
constants: c_vkorg_6002 type VKORG value '6002',
 c_vtweg_60 type VTWEG value '60',
 c_spart_60 type SPART value '60',
 c_msgfn_004 type msgfn value '004'.
FIELD-SYMBOLS <unicode_x1> type c.
FIELD-SYMBOLS <unicode_x2> type c.
DEFINE move_casting.
 assign &1 to <unicode_x1> casting.
 assign &2 to <unicode_x2> casting.
 move <unicode_x1> to <unicode_x2>.
END-OF-DEFINITION.
CHECK NOT is_complex_structure IS INITIAL.
LOOP AT it_bapimtcs WHERE tabname = 'BSS_CENTI'
 AND relkey(32) =
 is_complex_structure-header-object_instance-bpartnerguid.
 CLEAR LV_FOUND.
 CLEAR LS_E1KNVVM.
 move_casting IT_BAPIMTCS-DATA LS_perfk.
 LOOP AT CT_IDOC_DATA WHERE SEGNAM = 'E1KNVVM'. "Hvis E1KNVVM
 LS_E1KNVVM = CT_IDOC_DATA-SDATA. "segmentet allerede
 LV_FOUND = 'X'. "eksisterer
 MOVe LS_perfk-zzperfk TO LS_E1KNVVM-perfk.
 CT_IDOC_DATA-SDATA = LS_E1KNVVM.
 MODIFY CT_IDOC_DATA.
 EXIT.
 ENDLOOP.
 IF NOT LV_FOUND = 'X'.
 CALL FUNCTION 'PI_BP_INIT_IDOC_STRUCTURES'
 IMPORTING
 ES_E1KNVVM = LS_E1KNVVM
 EXCEPTIONS
 OTHERS = 0.
 MOVe LS_perfk-zzperfk TO LS_E1KNVVM-perfk.
 LS_E1KNVVM-MSGFN = c_msgfn_004. "Beskeden indeholder ændringer
 LS_E1KNVVM-VKORG = c_vkorg_6002.
 LS_E1KNVVM-VTWEG = c_vtweg_60.
 LS_E1KNVVM-SPART = c_spart_60.
 CT_IDOC_DATA-SEGNAM = 'E1KNVVM'.
 CT_IDOC_DATA-SDATA = LS_E1KNVVM.
 APPEND CT_IDOC_DATA.
 ENDIF.
ENDLOOP.
I hope this helps. Otherwise, please ask again.
Rgds.
Anders

How to replicate data from custom field in SRM to ECC

Hi,
I am using SRM 5.0, as per my requirement i need to get data from SRM (Web GUI) through custom fields in "Confirm Goods",
and need to pass this data to ECC,
I found that Message type MBGMCR; IDOC Type u2013 MBGMCR01 can be used for passing the data from SRM to ECC,
How can i pass the new data to this IDOC in SRM
and how can i get the data from this IDOC in ECC
Please help.
Thanks in advance,
Jerin.
Edited by: Jerin Joseph on Jul 23, 2009 5:06 PM

Hello,
This will help you.
Re: Replicating GR custom fields from EBP to SAP R/3
Thanks
Ashutosh

Steps for replicating GR custom field values from EBP to SAP R/3

Dear SRM Gurus,
We wre using SRM 5.0 extended classic scenario..
We are having 3 custom fields for GR in SRM, we want to replicate these values to 3 other standard fields in SAP R/3..
Can you pls tell us the Procedure, Steps and standard objects that has to be changed for replicating the GR field values from SRM to SAP R/3(4.6C).
Thanks in advance,
Chandra Sekhar.

Hi
Please go through the following links ->
Re: Confirmation screen field to be mapped to backend field
Re: Creating Confirmations in SRM - What is the preferred method
Re: GRN IDOC Transfer to ERP - MBGMCR01 ( 2 IDOCS created)
Re: Problem to send idoc for a Good Receipt created
GR IDOC Number
Re: Idoc error in Goods confirmation - urgent
Re: Delete goods confirmation in SRM3.0
Re: SRM / MM integratuion: goods receipt
IDOC MBGMCR01: CO Ctd-pedido exceeded by 1 UN:
Some useful SAP OSS Notes to refer ->
Note 521488 - FAQ: MB_CREATE_GOODS_MOVEMENT
Note 521427 - FAQ: IDocs for goods movements
Note 521488 - FAQ: MB_CREATE_GOODS_MOVEMENT
Hope this will definitely help.
Regards
- Atul

Replicating GR custom fields from EBP to SAP R/3

Dear SRM Gurus,
We are using SRM 5.0, extended classic scenario..
We have created 3 custom fields for GR in SRM and we want to pass these custom field values to SAP R/3(4.6C). Is there any BAdI or function module to replicate these custom field values from SRM 5.0 to SAP R/3.
Please do the needful..
Thanks in Advance,
Chandra Sekhar.

Hi
Please go through the following links ->
Re: Confirmation screen field to be mapped to backend field
Re: Creating Confirmations in SRM - What is the preferred method
Re: GRN IDOC Transfer to ERP - MBGMCR01 ( 2 IDOCS created)
Re: Problem to send idoc for a Good Receipt created
GR IDOC Number
Re: Idoc error in Goods confirmation - urgent
Re: Delete goods confirmation in SRM3.0
Re: SRM / MM integratuion: goods receipt
IDOC MBGMCR01: CO Ctd-pedido exceeded by 1 UN:
Some useful SAP OSS Notes to refer ->
Note 521488 - FAQ: MB_CREATE_GOODS_MOVEMENT
Note 521427 - FAQ: IDocs for goods movements
Note 521488 - FAQ: MB_CREATE_GOODS_MOVEMENT
Hope this will definitely help.
Regards
- Atul

IDOC customer fields

Similar Messages

Maybe you are looking for