Transfer Custom OM Infotype data through ALE for HRMD_ABA Message type
Hello Folks,
I have created a Custom OM Infotype.When i run the PFAL transaction. All the standard infotype data is getting filled, but i dont see custom infotype data getting filled.
Example: HRP9001 is the custom infotype.
Please let me know the step by step process to populate the Custom infotype data in ALE Transfer.
Thanks & Regards,
Nishanth Kumar
I think function module RH_MASTER_IDOC_DISTRIBUTE_HRMD shows some odd behaviour. It calls EDI_DOCTYPS_OF_MESTYP, which returns the name of the extension in an internal table named "doctyps". But later on, function module MASTER_IDOC_DISTRIBUTE is called with a structure "f_idoc_control". In this structure, the field "cimtyp" should hold the name of the extension, but it NEVER gets filled, although the value is present in doctyps-cimtyp.
So what I have done, is to activate userexit #004, which is called just before MASTER_IDOC_DISTRIBUTE and modifies structure f_idoc_control, if desired.
Call transaction CMOD and create a project in a non-SAP namespace: Zxxxx. The enhancement we need is "RHALE001" (HR-CA: Enhancement for ALE functionality in HR). One of its components is EXIT_SAPLRHA0_004, which consists of include ZXHALU08. In this include I called EDI_DOCTYPS_OF_MESTYP again to fill f_idoc_control-cimtyp.
Here is my code for include ZXHALU08
DATA: z_doctyps TYPE STANDARD TABLE OF edidocs WITH HEADER LINE.
CALL FUNCTION 'EDI_DOCTYPS_OF_MESTYP'
EXPORTING
mestyp = f_idoc_control-mestyp
TABLES
doctyps = z_doctyps
EXCEPTIONS
invalid_mestyp = 1
OTHERS = 2.
IF sy-subrc = 0.
LOOP AT z_doctyps.
f_idoc_control-cimtyp = z_doctyps-cimtyp.
ENDLOOP.
ENDIF.
Hope this helps
Similar Messages
-
How to add custom infotype in ALE for HRMD_A message type
Hi Friends-
Pls help me for our req we are using HRMD_A Message Type for HR master data but now we need to add one custom infotype ( 9902 ) also in standard ALE filters for this message type how i can do that pls let me know ?
<<removed_by_moderator>>
Regards
Meeta & Glory
Edited by: Vijay Babu Dudla on Dec 14, 2008 11:38 PMHi
Thanks for your support,
Pls let me know which steps i should go ? my secanrio is inbound side only,
step 1 ) Define idoc extension for HRMD_A01 using WE30 transaction and define it in partner profiles
step 2) do i need to write some code in BADI also to update information for my custom infotype also if yes then where and which BADI pls let me know ? because already am working on one badi HRALE00INBOUND_IDOC for few validation for incoming data.
step 3 ) add this new custom infotype in my standard ALE filters.
Pls let me know if am mistaking some where or if i have to do some thing else ?
Regards
Meeta & Glory -
Problem in BD64 for HRMD_ABA message type
Hi,
Iam using HRMD_ABA Message Type in distribution model(BD64).
My requirement is that i want to add status of the employment in the Filter Group.
i.e.: in BD64 transaction>under HRMD_ABA>data filter active>filter group>infotype-->(will be 0000)
-->Object type(Will be 'P' for person)
Now where i will put status value as '3'.....?
Thanks in advance..
Regards.HI,
it seems you have to add new filter objects.
Check tcode BD95 and BD59 to add new filter objects. -
Transfer of Classes( Classification data) - through ALE
Hi experts,
I am trying to transfer Classes from a 3.1i system to a ECC 6.0 system through ALE distribution.
Almost all the classes got transferred but in a few of the classes, the status of the idoc remains at 64 - waiting to be processed.
When I scheduled the processing of these idocs in background mode they result in a dump.
Dump:
The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
caught in
procedure "MAINTAIN_ALLO_VALUES_VIA_API" "(FORM)", nor was it propagated by a
RAISING clause.
This dump is happening because sy-index value is crossing 2147483647 ( which is the max allowed value).
I could not find any relevant notes for it. Does anyone know what is causing this issue and how to correct it.
FYI - There are around 3000 values attached to a characteristic which is attached to the class.
Thanks and Regards,
KarthikHi Karthrik,
Did you never get answer on this topic or did you make a request to SAP in the meanwhile? I got same dump and I am looking for solution, too.
Br
Markku -
TCODES FOR SENDINGIG AND RECEIVING DATA THROUGH ALE
Hi,
All,
Message type I can find for the following :
Equipment master: EQUIPMENT_CREATE
Work centre: WORKC2, WORKC3 or WORKC4
Functional location: FUNC_LOC_CREATE
but i did'nt find a transaction code for sending and receiving data through ALE.
For example: Send material T.code BD10,
Receive material T.code BD11.
Please give the solution.
Regards.can Tx BD21 is of any help
-
Uploading data in MM01 for different material types
Hi,
I have a doubt regarding uploading the data in MM01 for different material types.
Generally in MM01, we have different views for different material types. The number of views will vary depending upon the material type that we select.
I have a scenario, where in to upload the data, I have a flat file that consists of data for different message types. So, how to upload the data in such case.
Can anyone help me on the same by providing explanation or sample code...? What would be the possible ways to upload data in such scenario.
That would be of great help.
Thanks & Regards,
Pradeep.See the below code and use FM SELECTION_VIEWS_FIND..
REPORT zjpmuim306 NO STANDARD PAGE HEADING LINE-SIZE 250 MESSAGE-ID
zjpm001.
*& I N B O U N D V I A A B A P : Batch input Session method *
*& Development ID: IM_DD_306_LJP *
*& Report : ZJPMUIM306 *
*& The Purpose of the Object is to interface Create Input Record *
*& for SAP Migration from the Material master of BPCS All the *
*& information received at BPCS is collected into a single record. *
*& By using session method upload data from file ,one item is
*& created for one record *
*& Change Log: *
*& Init Who Date Text *
*& MALIKDH1 Seshu Reddy 26-07-2003 Initial Version *
Constants *
CONSTANTS:c_vkorg(4) type c value 'JP20', " Sales Organization
c_vtweg(2) type c value 'TR' , " Distribution Channel
c_werks(4) Type c value 'JP01' , " Plant
c_viewlist(15) VALUE 'KDEALBSZXVPCFQG'," View list
c_scm_view TYPE msichtausw-dytxt VALUE 'SCM View',
c_sd_view TYPE msichtausw-dytxt VALUE 'SD View',
c_seq_code(2) VALUE 'Z1', " Sequential Code
c_keep(1) TYPE c VALUE 'X', " Keep
c_group LIKE apqi-groupid VALUE 'IM306', " Session Name
c_tcode LIKE tstc-tcode VALUE 'MM02', " Transaction Code
c_blank(1) VALUE ' ', " Blank
c_intls(1) VALUE 'N'. " Logistic Status
Variables *
DATA: g_flag1(1), " Variable to hold
g_flag(1), " Variable to hold
g_file LIKE rlgrap-filename VALUE
'C:\Documents and Settings\seshur\Desktop\HCLT123.CSV'. " File name
Internal tables/ Work area *
Internal Table for Delimter
DATA : BEGIN OF t_delim OCCURS 0,
text(1000),
END OF t_delim.
Internal table for BDC processing
DATA : t_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
Internal table for holding the data which has to be uploaded.
DATA: BEGIN OF t_bpcs OCCURS 0,
matnr(15) TYPE c, " material no
dosage(40) TYPE c, " Dosage form(Local)
appearance(40) TYPE c, " Appearance
idcode(6) TYPE c, " Identification Code
prostformno(10) TYPE c, "SOP
weitab(7) TYPE c, " Weight/tablet
uom1(2) TYPE c, " UOM of Carton
uom2(2) TYPE c, " UOM of Case
carsize(14) TYPE c, " Carton size
cassize(14) TYPE c, " Case size
rupqty(11) TYPE c, " Round up
abvname(3) TYPE c, " Product short name
END OF t_bpcs.
*Internal table for t_bpcs
DATA: BEGIN OF t_mdata OCCURS 0,
matnr LIKE marc-matnr, " Material number
zzjp_dos_frm LIKE marc-zzjp_dos_frm, " Dosage form(Local)
zzjp_aprn LIKE marc-zzjp_aprn, " Appearance
zzjp_con_id LIKE marc-zzjp_con_id," Identification Code
zzjp_nyu_sop LIKE marc-zzjp_nyu_sop,"SOP
zzjp_wei_tab(10) type c , " Weight/tablet
zzjp_bio LIKE marc-zzjp_bio,"Biologics Indicator
zzjp_itf LIKE marc-zzjp_itf, " ITF code
zzjp_car(2) type c, " UOM of Carton
zzjp_cas(2) type c, " UOM of Case
zzjp_car_size(11) type c," Carton size
zzjp_cas_size(11) type c, " Case size
zzjp_rupqty(11) type c, " Round up
zzjp_init_ls LIKE marc-zzjp_init_ls, " Logistic Status
zzjp_re1 LIKE marc-zzjp_re1, "Document type(Local)
zzjp_re2 LIKE marc-zzjp_re2, "Report type
zzjp_re3 LIKE marc-zzjp_re3, "Shipping report type
zzjp_pro_id LIKE mvke-zzjp_pro_id," Product output sequence
zzjp_bu_id LIKE mvke-zzjp_bu_id, " Business unit indicator
zzjp_abv_name LIKE mvke-zzjp_abv_name," Product short name
zzjp_abv_id1 LIKE mvke-zzjp_abv_id1," Product short name output
zzjp_abv_id2 LIKE mvke-zzjp_abv_id2," Product short name internal
zzjp_spl_id LIKE mvke-zzjp_spl_id, " Sample internal order
END OF t_mdata.
Internal table for Mara Table
DATA: BEGIN OF t_mara OCCURS 0,
matnr LIKE mara-matnr, " material Number
vpsta LIKE mara-vpsta, " Maintenance status of complete material
pstat like mara-pstat, " Maintenance status
END OF t_mara.
Internal table for Material Master View Selection Screens
DATA: BEGIN OF t_bildtab OCCURS 0.
INCLUDE STRUCTURE mbildtab.
DATA: END OF t_bildtab.
internal table for T_bildtab
DATA: t_bildtab_dup LIKE t_bildtab OCCURS 0 WITH HEADER LINE.
*Work area for T_bildtab internal table(Views Selection)
DATA: BEGIN OF w_data,
flag1 type c,
anzd70 TYPE i,
field1(20) type c,
field2(20) type c,
field3(20) type c,
field4(20) type c,
count(2) TYPE c,
END OF w_data.
Main Processing *
START-OF-SELECTION.
Store data from file into internal table
PERFORM f_uplaod_data.
Transfer the uploaded data into t_mdata internal Table
PERFORM f_process_data.
Selecting The views based on Material number
PERFORM f_view_list.
Open a BDC Session
PERFORM f_bdc_open.
*Selecting the fields from mara table
SELECT matnr
vpsta
pstat
FROM mara
INTO TABLE t_mara
FOR ALL ENTRIES IN t_mdata
WHERE matnr = t_mdata-matnr.
SORT t_mara BY matnr.
SORT t_mdata BY matnr.
Transfer the uploaded data into BDCDATA structure
PERFORM f_process_bdc.
Close The BDC Session
PERFORM f_close_group.
*& Form F_VIEW_LIST *
Routine to used for Calling the function module *
Selection_views_find *
FORM f_view_list.
CALL FUNCTION 'SELECTION_VIEWS_FIND'
EXPORTING
bildsequenz = c_seq_code
pflegestatus = c_viewlist
TABLES
bildtab = t_bildtab
EXCEPTIONS
call_wrong = 1
empty_selection = 2
OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " F_VIEW_LIST
*& Form f612_view_sort *
Routine to used for Selecting The views based on Material Number *
FORM f612_view_sort.
t_bildtab_dup[] = t_bildtab[].
Reading the Internal table t_mara
READ TABLE t_mara WITH KEY matnr = t_mdata-matnr.
TRANSLATE t_mara-pstat USING ' $'.
CLEAR: w_data-flag1, w_data-anzd70.
LOOP AT t_bildtab_dup.
IF t_bildtab_dup-pstat CA t_mara-pstat.
w_data-anzd70 = w_data-anzd70 + 1.
IF t_bildtab_dup-kzanz IS INITIAL.
t_bildtab_dup-kzanz = 'X'.
w_data-flag1 = 'X'.
MODIFY t_bildtab_dup.
ENDIF.
ELSE.
IF NOT t_bildtab_dup-kzanz IS INITIAL.
CLEAR t_bildtab_dup-kzanz.
w_data-flag1 = 'X'.
MODIFY t_bildtab_dup.
ENDIF.
ENDIF.
ENDLOOP.
TRANSLATE t_mara-pstat USING '$ '.
IF NOT w_data-flag1 IS INITIAL.
SORT t_bildtab_dup BY kzanz DESCENDING idxbd ASCENDING.
ENDIF.
*Reading The internal table for T_bildtab_dup
READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
IF t_bildtab_dup-kzanz = 'X'.
WRITE sy-tabix TO w_data-count.
w_data-count = w_data-count + 2.
IF w_data-anzd70 > 18.
w_data-count = w_data-count - 18.
ENDIF.
CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field1.
CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field2.
ENDIF.
READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
IF t_bildtab_dup-kzanz = 'X'.
WRITE sy-tabix TO w_data-count.
IF w_data-anzd70 > 18.
w_data-count = w_data-count + 2.
w_data-count = w_data-count - 18.
ENDIF.
CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field3.
CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field4.
ENDIF.
ENDFORM. " f612_view_sort
*& Form f_uplaod_data *
Routine to used for Uploading the data from file to Internal table *
FORM f_uplaod_data.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
filename = g_file
filetype = 'DAT'
TABLES
data_tab = t_delim
EXCEPTIONS
conversion_error = 1
file_open_error = 2
file_read_error = 3
invalid_type = 4
no_batch = 5
unknown_error = 6
invalid_table_width = 7
gui_refuse_filetransfer = 8
customer_error = 9
OTHERS = 10.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF t_bpcs IS INITIAL.
LOOP AT t_delim.
SPLIT t_delim-text AT ',' INTO t_bpcs-matnr
t_bpcs-dosage
t_bpcs-appearance
t_bpcs-idcode
t_bpcs-prostformno
t_bpcs-weitab
t_bpcs-uom1
t_bpcs-uom2
t_bpcs-carsize
t_bpcs-cassize
t_bpcs-rupqty
t_bpcs-abvname.
APPEND t_bpcs.
ENDLOOP.
ENDIF.
ENDFORM. " f_uplaod_data
*& Form F_BDC_OPEN
Routine to create BDC Session to be processed
FORM f_bdc_open.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
client = sy-mandt
group = c_group
keep = c_keep
user = sy-uname
EXCEPTIONS
client_invalid = 1
destination_invalid = 2
group_invalid = 3
group_is_locked = 4
holddate_invalid = 5
internal_error = 6
queue_error = 7
running = 8
system_lock_error = 9
user_invalid = 10
OTHERS = 11.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
MESSAGE S000 WITH 'Batch input session is created successfully'(T02).
ENDIF.
ENDFORM. " F_BDC_OPEN
*& Form F_PROCESS_BDC
Processing of BDCDATA Structure
FORM f_process_bdc.
LOOP AT t_mdata.
PERFORM f612_view_sort.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0060'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'RMMG1-MATNR'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=AUSW'.
PERFORM f_bdc_field USING 'RMMG1-MATNR'
t_mdata-matnr.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'MSICHTAUSW-DYTXT(01)'.
IF w_data-anzd70 > 18.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=P+'.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
ENDIF.
reading the t_bildtab internal table
READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
IF t_bildtab_dup-kzanz = 'X'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
w_data-field1.
PERFORM f_bdc_field USING w_data-field2 'X'.
g_flag = 'X'.
ENDIF.
reading the t_bildtab internal table
READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
IF sy-subrc EQ 0.
g_flag = 'X'.
ENDIF.
IF t_bildtab_dup-kzanz = 'X'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
w_data-field3.
PERFORM f_bdc_field USING w_data-field4 'X'.
g_flag1 = 'X'.
ENDIF.
IF g_flag = 'X' AND g_flag1 = 'X'.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0080'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'RMMG1-VTWEG'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=ENTR'.
PERFORM f_bdc_field USING 'RMMG1-WERKS'
c_werks.
PERFORM f_bdc_field USING 'RMMG1-VKORG'
c_vkorg.
PERFORM f_bdc_field USING 'RMMG1-VTWEG'
c_vtweg.
CLEAR g_flag.
CLEAR g_flag1.
ELSE.
IF g_flag = 'X'.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0080'.
PERFORM f_bdc_field USING 'RMMG1-WERKS'
c_werks.
PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
ELSE.
IF g_flag1 = 'X'.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0080'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'RMMG1-VTWEG'.
PERFORM f_bdc_field USING 'RMMG1-WERKS'
c_werks.
PERFORM f_bdc_field USING 'RMMG1-VKORG'
c_vkorg.
PERFORM f_bdc_field USING 'RMMG1-VTWEG'
c_vtweg.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=ENTR'.
ENDIF.
ENDIF.
ENDIF.
*Processing of SCM View
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '4000'.
PERFORM f_bdc_field USING 'BDC_CURSOR' 'MARC-ZZJP_DOS_FRM'.
PERFORM f_bdc_field USING 'MARC-ZZJP_DOS_FRM'
t_mdata-zzjp_dos_frm.
PERFORM f_bdc_field USING 'MARC-ZZJP_APRN'
t_mdata-zzjp_aprn.
PERFORM f_bdc_field USING 'MARC-ZZJP_CON_ID'
t_mdata-zzjp_con_id.
PERFORM f_bdc_field USING 'MARC-ZZJP_NYU_SOP'
t_mdata-zzjp_nyu_sop.
PERFORM f_bdc_field USING 'MARC-ZZJP_WEI_TAB'
t_mdata-zzjp_wei_tab.
PERFORM f_bdc_field USING 'MARC-ZZJP_CAR'
t_mdata-zzjp_car.
PERFORM f_bdc_field USING 'MARC-ZZJP_CAS'
t_mdata-zzjp_cas.
PERFORM f_bdc_field USING 'MARC-ZZJP_CAR_SIZE'
t_mdata-ZZJP_CAR_SIZE.
PERFORM f_bdc_field USING 'MARC-ZZJP_CAS_SIZE'
t_mdata-ZZJP_CAS_SIZE.
PERFORM f_bdc_field USING 'MARC-ZZJP_RUPQTY'
t_mdata-ZZJP_RUPQTY.
PERFORM f_bdc_field USING 'MARC-ZZJP_BIO'
t_mdata-zzjp_bio.
PERFORM f_bdc_field USING 'MARC-ZZJP_ITF'
t_mdata-zzjp_itf.
PERFORM f_bdc_field USING 'MARC-ZZJP_INIT_LS'
t_mdata-zzjp_init_ls.
PERFORM f_bdc_field USING 'MARC-ZZJP_RE1'
t_mdata-zzjp_re1.
PERFORM f_bdc_field USING 'MARC-ZZJP_RE2'
t_mdata-zzjp_re2.
PERFORM f_bdc_field USING 'MARC-ZZJP_RE3'
t_mdata-zzjp_re3.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'/00'.
*Processing of SD View
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '4000'.
PERFORM f_bdc_field USING 'BDC_CURSOR' 'MVKE-ZZJP_PRO_ID'.
PERFORM f_bdc_field USING 'MVKE-ZZJP_PRO_ID'
t_mdata-zzjp_pro_id.
PERFORM f_bdc_field USING 'MVKE-ZZJP_BU_ID'
t_mdata-zzjp_bu_id.
PERFORM f_bdc_field USING 'MVKE-ZZJP_ABV_NAME'
t_mdata-zzjp_abv_name.
PERFORM f_bdc_field USING 'MVKE-ZZJP_ABV_ID1'
t_mdata-zzjp_abv_id1.
PERFORM f_bdc_field USING 'MVKE-ZZJP_ABV_ID2'
t_mdata-zzjp_abv_id2.
PERFORM f_bdc_field USING 'MVKE-ZZJP_SPL_ID'
t_mdata-zzjp_spl_id.
PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
PERFORM f_bdc_dynpro USING 'SAPLSPO1' '0300'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=YES'.
perform f_bdc_insert.
REFRESH T_BDCDATA.
ENDLOOP.
ENDFORM. " F_PROCESS_BDC
*& Form f_bdc_dynpro
p_prog is the program name to which data is passed *
p_dyno is the screen number to which the data is passed
Routine for populating the BDCDATA structure with the
Screen related information
FORM f_bdc_dynpro USING p_prog
p_dyno.
t_bdcdata-program = p_prog.
t_bdcdata-dynpro = p_dyno.
t_bdcdata-dynbegin = 'X'.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM. " F_bdc_dynpro
*& Form F_BDC_FIELD
p_fnam is the field name to which value is passed
p_fval is the field value which is passed
p_fnam is the field name to which value is passed
p_fval is the field value which is passed
FORM f_bdc_field USING p_fnam
p_fval.
t_bdcdata-fnam = p_fnam.
t_bdcdata-fval = p_fval.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM. " F_bdc_field
*& Form F_PROCESS_DATA *
Routine to used for moving data from T_bpcs internal table to *
t_mdata Internal Table *
FORM f_process_data.
LOOP AT t_bpcs.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = t_bpcs-matnr
IMPORTING
output = t_mdata-matnr.
MOVE t_bpcs-dosage TO t_mdata-zzjp_dos_frm.
MOVE t_bpcs-appearance TO t_mdata-zzjp_aprn.
MOVE t_bpcs-idcode TO t_mdata-zzjp_con_id.
MOVE t_bpcs-prostformno TO t_mdata-zzjp_nyu_sop.
MOVE t_bpcs-weitab TO t_mdata-zzjp_wei_tab.
MOVE c_blank TO t_mdata-zzjp_bio.
MOVE c_blank TO t_mdata-zzjp_itf.
MOVE t_bpcs-uom1 TO t_mdata-zzjp_car.
MOVE t_bpcs-uom2 TO t_mdata-zzjp_cas.
MOVE t_bpcs-carsize TO t_mdata-zzjp_car_size.
MOVE t_bpcs-cassize TO t_mdata-zzjp_cas_size.
MOVE t_bpcs-rupqty TO t_mdata-zzjp_rupqty.
MOVE c_intls TO t_mdata-zzjp_init_ls.
MOVE c_blank TO t_mdata-zzjp_re1.
MOVE c_blank TO t_mdata-zzjp_re2.
MOVE c_blank TO t_mdata-zzjp_re3.
MOVE c_blank TO t_mdata-zzjp_pro_id.
MOVE c_blank TO t_mdata-zzjp_bu_id.
MOVE t_bpcs-abvname TO t_mdata-zzjp_abv_name.
MOVE c_blank TO t_mdata-zzjp_abv_id1.
MOVE c_blank TO t_mdata-zzjp_abv_id2.
MOVE c_blank TO t_mdata-zzjp_spl_id.
APPEND t_mdata.
ENDLOOP.
ENDFORM. " F_PROCESS_DATA
*& Form f_bdc_close
Routine to close the BDC Session
FORM f_close_group.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
not_open = 1
queue_error = 2
OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " f_close_group
*& Form f_bdc_insert
routine to input batch data into the Transaction MM02 from the
session created
FORM f_bdc_insert.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
tcode = c_tcode
TABLES
dynprotab = t_bdcdata
EXCEPTIONS
internal_error = 1
not_open = 2
queue_error = 3
tcode_invalid = 4
printing_invalid = 5
posting_invalid = 6
OTHERS = 7.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " f_bdc_insert
Reward Points if it is useful
Thanks
Seshu -
Filter Infotypes based on Company Code for the Message Type HRMD_A
Hi,
I have a requirement to send different infotypes for different Company codes using the same distribution model for the message type HRMD_A.
Example :
For the BUKRS 2500 I need to send infotype 0000 ,0002,0006
For the BUKRS 2600 I need to send infotype 0000 ,0008,0009
It will be a great help for me if any one can guide me on that.
Regards,
RakaHi ,
Thanks for the reply.
I alredy have done that . But its not working.
Its working only for infotype 0001.
If the infotype is there in any of the filter groups, the data will be sent irrespective of the Com Code.
Regards,
Raka -
IDoc Error: No recipient found for IDoc message type in the ALE model...
Hello Experts,
I just created an IDoc for purchase orders and when I try to test it after releasing
the PO, an error is shown in the processing log saying that there are no recipients
found for my message type of the IDoc. I refrenced it against a working IDoc but I might be
missing something.
Hope you can help me guys. Thank you and take care!hi,
in bd64 ,goto change mode select ur distribution model and click add message type define ur logical systems and message type and save.
thn goto environment - partner profiles - f 8.it will show whether model is created or any errors.
then go back edit - model view - distribute.
reward points if hlpful. -
IDOC Segment missing for MATMASS Message type
Through change pointer program for the message type YAUIHUBMATMAS IDOC is triggered.
1) Change pointers are defined in system for the message type T Code u2013 BD52.
2) If respective field is changed in material master , this data is stored in change pointers table BDCP.
3) Background jobs are scheduled every day, which searches for the changes pointer table and triggers the idoc.
In our case IDOC is getting generated but with one segment missing.
We have analysed the succesful and failed IDOC and found desrepency is field updation of BDCP table.
Succesful case contain material number in object value of ZZMDST field where as failed contain some other value.
Can anyone please help us to guide how the BDCP table is updated and the values are mapped in it or any other suggestion to find why the segment is missing in it.
Regards,
Roshni.Jürgen L. wrote:
> I have never seen a YAUIHUBMATMAS IDOC, nor a ZZMDST field .
> This seems to be home made.
>
> You are expecting that standard SAP programs are generating change pointers for your z-fields?
> Do you see a change history in material master for your z-field?
>
>
> follow the slution from this thread:
>
Yes ,This is a Z -field.
Change pointer is triggering the idoc fo this Z-field but in some cases one segment is missing .
This is z-field in the basic data view of material master.
Yes , we have checked the change history in material master for this field it is getting updated there in BDCP table as well but in BDCP table if this field is flagged then object value is not contain material number instead it contain some other number .
But in case of succesful IDOC the object value is same as material number.
Regards,
Roshni -
Need help for new message type for PO archiving
Hello All
I have configured new message type ZARR for PO archiving process. After configuring all the steps this condition is not getting picked to by itself. And after maintaing it manually it is giving red flag without any error message. Here I am listing all the step that I have followed for config. Please help me am I missing something or any parameter is wrong.
Steps for new Message Type for PO Archiving
1. Defined new Table 513 Purch.Org./Plant.
2. Defined new access sequence Z513 Access Sequence for Archiving.
Following are parameters to the Access Sequence
Access Sequence Number = 21
Table = 513
Description = Purch.Org./Plant
Requirement = 101
Exclusive = Yes (box checked)
3. Maintain Output Type ZARR for PO
General Data
Access Sequence = Z513
Access to condition (Checked)
Multiple Issuing (Checked)
Program = FM06AEND
FORM Routine = CHANGE_FLAG
Default Values
Dispatch Time = Send Immediately (when saving application)
Transmission Medium = Print Out
Storage System
Storage Mode = Archive Only
Document Type = ARCHIVE
Mail Title and texts
Language = EN
Title = Archiving for Legal Requirement
Processing Routines
Transmission Medium = 1 (Print Out)
Program = SAPFM06P
Form Routine = ENTRY_NEU
Form = ZJ_9H_MEDRUCK
Partner Roles
Medium = Print Out
Funct = VN
Name = Vendor
4. Fine-Tuned Control: Purchase Order
Oprat. = 1
CType = ZARR
Name = Testing for Archivin
Short Text = New
Update Print Related Data = Yes (checked)
Oprat. = 2
CType = ZARR
Name = Testing for Archivin
Short Text = Change
Update Print Related Data = Yes (checked)
5. Maintain Message Determination Schema: Purchase Order
Procedure RMBEF1
Step = 100
Cntr = 1
CTyp = ZARR
Description = Testing for Archivin
Requirement = 101
6. Assign Schema to Purchase Order
Procedure RMBEF1
7. Define Partner Roles for Purchase Order
Out. = ZARR
Med = 1 (Printout)
Funct = VN
Name = Testing for Archivin
Name = Vendor
8. Test Condition Maintained in MN04 (Master Data)
Purch. Org. = 0001
Plant = 24
Partner Funct = VN
Medium = 1 (Printout)
Date/Time = 4 Send immediately (when saving application)
Output Device = HUL1
Storage Mode = Archiving only
Thanks
Ankitthe problem is the Exclusive = Yes indicator in the access sequence.
Your other message has this exclusive indicator as well.
so if the first message is found, then no other message wil be determined
to allow several messages in one PO, you must not set this exlusive indicator -
Create 2 outbound Idocs for 1 message type
Hi Experts,
We are sending an outbound Idoc of message type DESADV. We would like to trigger 2 Idocs per Shipping Notification.
Could you please help?
Thanks,
Vitish.Hello Vitish
Each output partner can have it's own output. Also for the same message type. Maybe the 2 DESADV IDOC's are sent to different partners or destinations. But even when not you still can define 2 different output partners for the message type. Then 2 outputs will be triggered for the same message type.
Regards Jack -
Finding Process Code for a message Type
Hi,
Is there any way to find process code for a specific message type.
Message Type WFRESOURCE_CHANGEAVAILABILITYHi Swathi,
I have already mention the process codes that can be used for this message type. For your convenience i am also attaching th description ,which process code can be used when.
ABI_AIDN_IN Auto- ID Idoc process
ED00 Display Idoc using work item
ED00_XML Display idoc using work item (xml)
ED08 Forward idoc
ZABI_DLV_IN Delivery advice ( AIDDESADV with DELVRY04)
Regards
Vinod -
Need to load the data through excel for plan data through IP?
Hi all,
The user needs to load the data through the excel and click on the save button so that the data is saved in the cube through integrated planning.
The objects used are
customer, material, plant, calendarmonth sales qty, gross billing!!
Can anyone pls let me know how to do this?
ThanksHi,
You can use the following How to guide to load data from file into transactional cube.
If using IP :
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90cef248-29e0-2910-11bb-df8dece7e22c?quicklink=index&overridelayout=true
Can also Refer to Marc's Blog:
/people/marc.bernard/blog/2007/11/25/how-to-load-a-file-into-sap-netweaver-bi-integrated-planning-part-1
If you are using bPS you can get the details in Wiki also for the same.
You can then create the hyperlink in Excel ,which user can use to upload data which can then be saved to cube using save button. -
Transfer of inforecord condition records through ALE
Hi,
I want to know how to transfer Info record condition types other than PB00 through ALE.e.g. FRA1,Z cond. types etc.
Thanks,
KaveriHi,
Transaction VK13, you check if this one suits your requirement.
Thanks
Krithika -
ALE - Status 52 Idocs for HRMD_A message type
HRMD_A Idocs in target system are not completely posted, turning into status '52'. Most of the times the infotype 1001 idoc with relations ship P->S arrives before the idoc which has the actual objects(P, S) causing 'Relationship imposible because the object does not exist". We use program RBDAPP01 for inbound processing of Idoc which should take care of Serialization based on the time stamp of idoc creation in source system.
Change pointors for Message type HRMD_A are processed using program RBDMIDOC in source system.
It is unlikely that relationship P->S is created without object P being created in the source system. So the change pointors should create the idocs in the same sequence. But it is not happening.
Any help on this appreciated.Hi Santosh,
If you haven't found by now the .... here is the Solution:
First change the size of table T77S0 check out note 305688
Then process the IDOCS again - check out note 363187
Regards
Luis
Maybe you are looking for
-
Hi, Where is the com.sapportals.portal.prt.service.license.ILicenseService jar loacted? Many thanks, Dharmi
-
How to make iTunes support more than just one harddrive
The title of this topic says it all: How do I make iTunes support more than just one harddrive? I cannot afford to buy a really huge drive just because iTunes doesn't support more than one. There must be a way around this! Anyone?
-
Can't see Macintosh HD when trying to reinstall
In short: Trying to reinstall Yosemite after erasing disk, can't see Macintosh HD when asked to select install disk, can I lay see recovery (which is locked). Can see disk under disk utility but no Erase tab visible, only First Aid and Partition tabs
-
When using the text to speech which vtml_speed value is the best?
When using the text to speech function along with the VTML tag for speech (<vtml_speed>) what number provides the best rate for learning. I am currently trying to use this function to improve my computor generated speech for a project. I have been ge
-
ITunes doesn't see all photos in Adobe
Have 60GB iPod. 28GB music. I'm using iTunes 5.0 and Adobe Photoshop Elements 3.0. I have 11,000+ photos so I've created three collections in PSE with 50, 300 and 900 photos in each. Syncing iTunes to these three collections, iTunes only sees 475 pho