ALE RBDMIDOC dump
Hi All,
I am getting dump while running program RBDMIDOC for message type DEBMAS. The dump is ABAP/4 processor: DBIF_REPO_SQL_ERROR. Can any one have idea why this is occuring? Thanks in advance for your valuble suggestion
Hi Jaiganesh,
You can try out folowing t-codes for error debugging
1.bd75
2.bdm2
3.sm58
4.bd87
RSEINB00 and RBAPP01 are the programs which are used to Post the IDOC to databse and process the inbound IDOC.
Also you can use following links for error debbuging
(1) /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
(2) /people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
(3)http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
(4) idoc
(5)http://help.sap.com/saphelp_erp2005vp/helpdata/en/78/2178a651ce11d189570000e829fbbd/frameset.htm--
--This is for Message Control. See the Left Pane in this web page to get the ALE implementation for BAPI's also.
(6)/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment - Converson Rules Guidelines
(7)ALE Inbound Error Handling - Inbound Error Handling in ALE
Hope this solves your problem.
Note: Reward if useful
Similar Messages
-
ALE throws dump Message_Type_X
Hi All,
I did ALE configuration on my DEV and PRD for transferring data from DEV to PRD. Although i know, we should not move any data from DEV to PRD, but it's client requirement.
So i did ALE and model view successfully generated on DEV and RFC is perfectly fine even by connection test or authorization test.
When i run bd10 on DEV, it successfully generated idoc with message type MATMAS. and when i get the materail via BD11, it successfully created idoc on PRD. but when i see the material in MM03, it throws error material does not exist or is not activated.
it also throws dump Message_Type_X
WORKFLOW_LOCAL_400
RFC_READ_DESTINATION_TYPE
DESTINATION_NOT_EXIST
What steps should follow now?
Regards
DishaHi Krishnendu,
Status is in red when i check from t-code WE02.
When i check it in MM90 and execute it, it does not show any log.
Please tell if i am missing any step..
Regards
Disha -
Hi Experts,
I am getting error SYSTEM_IMODE_TOO_LARGE.
The program takes the change pointers and creates an IDOC. Only way now is to process change pointers mannually to reduce the number of change pointers for this program.
Can you suggest any way to process change pointer mannually and creating IDOCS. BD21 transaction is of no use because it is submitting RBDMIDOC.
Thanx
SushamaHi,
Refer
Go through the below thread.
SYSTEM_IMODE_TOO_LARGE runtime error
ABAP RuntimeError SYSTEM_IMODE_TOO_LARGE -
Dump run time error "dbif_rsql_sql_error"
Hi guru's,
I have a genric data source with function module which feeds data to a genric ods in bw.
But at time of data upload i see quality status in manage of ods green saying (0 of 0 records extracted) but it asks me to check dump in st22 which is as follows
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 21.11.2006 at 23:57:48
An SQL error occurred when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"ZL3_BW_SALES_ORDER_ITEM" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
How to correct the error
The exception must either be prevented, caught within the procedure
"ZL3_BW_SALES_ORDER_ITEM"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01555: snapshot too old: rollback segment
number 222 with name "_SYSSMU222$" too small"
Internal call code.........: "[RSQL/FTCH/VBAP ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"SAPLZL3_BW_VARIANT" or "LZL3_BW_VARIANTU03"
"ZL3_BW_SALES_ORDER_ITEM"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "wieap053"
Network address.......... "10.50.197.53"
Operating system......... "HP-UX"
Release.................. "B.11.23"
Hardware type............ "ia64"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "wieap007"
Database type............ "ORACLE"
Database name............ "P00"
Database owner........... "SAPR3"
Character set............ "en_US.iso88591"
SAP kernel............... "640"
Created on............... "May 21 2006 20:37:10"
Created in............... "HP-UX B.11.23 U ia64"
Database version......... "OCI_920 "
Patch level.............. "129"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "HP-UX B.11"
User, transaction...
Client.............. 001
User................ "RFC_P92"
Language key........ "E"
Transaction......... " "
Program............. "SAPLZL3_BW_VARIANT"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP program "SAPLZL3_BW_VARIANT" in
"ZL3_BW_SALES_ORDER_ITEM".
The main program was "SBIE0001 ".
The termination occurred in line 240 of the source code of the (Include)
program "LZL3_BW_VARIANTU03"
of the source code of program "LZL3_BW_VARIANTU03" (when calling the editor
2400).
The program "SAPLZL3_BW_VARIANT" was started as a background job.
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "ZL3_BW_SALES_ORDER_ITEM" "(FUNCTION)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLZL3_BW_VARIANT ". Its source code starts
in line 5
of the (Include) program "LZL3_BW_VARIANT$03 ".
Source code extract
002100 a~werks
002110 c~edatu
002120 a~aedat
002130 a~erdat
002140 FROM ( vbap AS a
002150 INNER JOIN vbak AS b
002160 ON a~vbeln = b~vbeln
002170 AND b~vbtyp = 'W' "C0006-R2
002180 INNER JOIN vbep AS c
002190 ON a~vbeln = c~vbeln
002200 AND a~posnr = c~posnr
002210 AND c~etenr = '1' )
002220 WHERE a~vbeln IN
002230 ( SELECT objectid
002240 FROM cdhdr
002250 WHERE objectclas = 'VERKBELEG'
002260 * AND tcode = 'VA02'
002270 AND udate IN l_r_aedat )
002280 OR a~erdat IN l_r_aedat.
002290
002300 ENDIF. "Full or Delta ?
002310 ENDIF. "First data package ?
002320
002330 * Fetch records into e_t_data
002340
002350 FETCH NEXT CURSOR s_cursor
002360 INTO CORRESPONDING FIELDS
002370 OF TABLE l_t_data
002380 PACKAGE SIZE s_s_if-maxsize.
002390
> IF sy-subrc <> 0.
00241 0
002420 CLOSE CURSOR s_cursor.
002430
002440 ** Do not insert the upload date in the timestamp table when testing on
002450 ** the R/3 system
002460 * IF SY-TCODE <> 'RSA3'
002470 * AND SY-TCODE <> 'RSO2'
002480 * AND SY-TCODE <> 'SE37'
002490 * AND I_READ_ONLY IS INITIAL.
002500 *
002510 * ls_zl3_bw_timest-upload_date = sy-datum.
002520 * ls_zl3_bw_timest-oltpsource = s_s_if-dsource.
002530 *
002540 * INSERT INTO zl3_bw_timest VALUES ls_zl3_bw_timest.
002550 *
002560 * ENDIF.
002570
002580 RAISE no_more_data.
002590 ENDIF.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 1
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM
SY-TITLE Data extraction using SUBMIT_JOB as batch process
SY-MSGTY E SY-MSGID BM
SY-MSGNO 026 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
9 FUNCTION ZL3_BW_SALES_ORDER_ITEM
SAPLZL3_BW_VARIANT
LZL3_BW_VARIANTU03 240
8 FUNCTION RSA3_GET_DATA_SIMPLE
SAPLRSA3
LRSA3U06 74
7 FORM EXTRACTOR_FETCH
%_T002T1
??? 0
6 FORM EXTRACT_EAPI_INTO_QUEUE
%_T002T1
??? 0
5 FUNCTION RSC1_DELTA_BIW_GET
SAPLRSC1
LRSC1U03 390
4 FORM DATA_TRANSFER
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7 128
3 FUNCTION RSAP_DATA_TRANSFER
SAPLRSAP
LRSAPU06 137
2 FUNCTION RSAP_PERFORM_EXTRACTION
SAPLRSAP
LRSAPU19 135
1 EVENT START-OF-SELECTION
SBIE0001
SBIE0001 60
Chosen variables
9 FUNCTION ZL3_BW_SALES_ORDER_ITEM
SAPLZL3_BW_VARIANT
LZL3_BW_VARIANTU03 240
I_DSOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
I_INITFLAG
2
0
I_MAXSIZE 050000
333333
050000
I_READ_ONLY
2
0
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
E_T_DATA[] Table IT_1937[0x103]
I_T_FIELDS[] Table IT_1917[13x30]
I_T_SELECT[] Table IT_1916[1x123]
<%_TABLE_CDHDR> ???
%_DUMMY$$
2222
0000
SY-REPID SAPLZL3_BW_VARIANT
5454543545554544452222222222222222222222
310CAC3F27F61291E40000000000000000000000
SYST-REPID SAPLZL3_BW_VARIANT
5454543545554544452222222222222222222222
310CAC3F27F61291E40000000000000000000000
<%_TABLE_ZL3_VARIANT_CONF> ???
L_R_AEDAT[] Table IT_1938[1x19]
%_SPACE
2
0
S_S_IF-MAXSIZE 050000
333333
050000
S_CURSOR 20
0001
0004
L_T_DATA[] Table IT_1939[0x111]
SY-SUBRC 0
0000
0000
SY-UZEIT 220930
333333
220930
L_T_DATA 00000000000000 ##
2222222222333333333333332222222222222200
0000000000000000000000000000000000000000
... + 40 ######
0000002222222222222222222222222222222222
00000C0000000000000000000000000000000000
... + 80 000000000000000000000000
2222222333333333333333333333333
0000000000000000000000000000000
%_PRINT 001SBIE0001_RFC
2222333544433335544222222222222222222222
000000132950001F263000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 X8 ###A###PX_PAPER DRF
2222222225320004000555545452222222222454
000000000880000100008F010520000000000426
... + 120 C_P92 LIST1S
4553322222222222222222222222222222445535
3F09200000000000000000000000000000C93413
... + 160 TEXT 1 5D 2 ###Y
545522222222323422222222222222320015
4584000000001054000000000000002000E9
L_T_DATA-AEDAT 00000000
33333333
00000000
8 FUNCTION RSA3_GET_DATA_SIMPLE
SAPLRSA3
LRSA3U06 74
I_CHABASNM
222222222222222222222222222222
000000000000000000000000000000
I_DATAPAKID 000000
333333
000000
I_INITFLAG
2
0
I_ISOURCE
222222222222222222222222222222
000000000000000000000000000000
I_MAXSIZE 000000
333333
000000
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
I_RLOGSYS
2222222222
0000000000
I_UPDMODE
22
00
E_T_DATA[] Table IT_1937[0x103]
I_T_FIELDS[] Table[initial]
I_T_SELECT[] Table[initial]
SY ########################################
0000000000000000000000000000000000000000
000100000001000100000000000A000000000000
... + 40 ###############A#######P################
0000000000000004000000050000000000000001
0001000000010001000100000000000000000003
... + 80 ###################g####################
0000000000000000000600000000000000000000
0000000000000000000700000000000000000000
... + 120 #######################################T
0000000000000000000000000000000000010005
0000000000000000000000000000000000060004
... + 160 ################ u############# E0X X1
0000000000000001270000000000000222435253
00000000000000E0050020000C0000C000508081
... + 200 000 ####__S 001
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000010
... + 240 80
222223322222222
000008000000000
S_S_IF_SIMPLE-T_FIELDS Table IT_1917[13x30]
S_S_IF_SIMPLE-T_SELECT Table IT_1916[1x123]
G_T_FIELDS Table[initial]
%_DUMMY$$
2222
0000
G_S_RODCHABAS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
22222222222222
00000000000000
SY-REPID SAPLRSA3
5454554322222222222222222222222222222222
310C231300000000000000000000000000000000
RSAL_S_LOGPARMS-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
G_T_LANGU Table[initial]
E_T_DATA 00000000000000 ##
2222222222333333333333332222222222222200
0000000000000000000000000000000000000000
... + 40 ######
0000002222222222222222222222222222222222
00000C0000000000000000000000000000000000
... + 80 0000000000000000
22222223333333333333333
00000000000000000000000
S_S_IF_SIMPLE-INITFLAG
2
0
S_FNAME ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
S_S_IF_SIMPLE-DSOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
SY-XFORM CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
SY-XPROG SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
S_S_IF_SIMPLE-MAXSIZE 050000
333333
050000
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
S_S_IF_SIMPLE-REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
%_PRINT 001SBIE0001_RFC
2222333544433335544222222222222222222222
000000132950001F263000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 X8 ###A###PX_PAPER DRF
2222222225320004000555545452222222222454
000000000880000100008F010520000000000426
... + 120 C_P92 LIST1S
4553322222222222222222222222222222445535
3F09200000000000000000000000000000C93413
... + 160 TEXT 1 5D 2 ###Y
545522222222323422222222222222320015
4584000000001054000000000000002000E9
G_S_INTERFACE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 000000 000000
2222222222333333222333333
0000000000000000000000000
SYST-REPID SAPLRSA3
5454554322222222222222222222222222222222
310C231300000000000000000000000000000000
7 FORM EXTRACTOR_FETCH
%_T002T1
??? 0
SYST-REPID %_T002T1
2553335322222222222222222222222222222222
5F40024100000000000000000000000000000000
E_T_DATA Table IT_1937[0x103]
SY-SUBRC 0
0000
0000
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGNO 026
333
026
%_DUMMY$$
2222
0000
SY-REPID %_T002T1
2553335322222222222222222222222222222222
5F40024100000000000000000000000000000000
6 FORM EXTRACT_EAPI_INTO_QUEUE
%_T002T1
??? 0
G_TABIX 1
0000
0001
SY ########################################
0000000000000000000000000000000000000000
000100000001000100000000000A000000000000
... + 40 ###############A#######P################
0000000000000004000000050000000000000001
0001000000010001000100000000000000000003
... + 80 ###################g####################
0000000000000000000600000000000000000000
0000000000000000000700000000000000000000
... + 120 #######################################T
0000000000000000000000000000000000010005
0000000000000000000000000000000000060004
... + 160 ################ u############# E0X X1
0000000000000001270000000000000222435253
00000000000000E0050020000C0000C000508081
... + 200 000 ####__S 001
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000010
... + 240 80
222223322222222
000008000000000
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
L_T_DATA Table IT_1937[0x103]
C_SUBRC 0
0000
0000
I_OSOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
5 FUNCTION RSC1_DELTA_BIW_GET
SAPLRSC1
LRSC1U03 390
I_CHABASNM
222222222222222222222222222222
000000000000000000000000000000
I_DATAPAKID 000000
333333
000000
I_INITFLAG
2
0
I_ISOURCE
222222222222222222222222222222
000000000000000000000000000000
I_MAXSIZE 000000
333333
000000
I_PRIVATE_MODE
2222
0000
I_READ_ONLY
2
0
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
I_RLOGSYS
2222222222
0000000000
I_UPDMODE
22
00
E_T_DATA[] Table IT_1926[0x103]
I_T_FIELDS[] Table[initial]
I_T_SELECT[] Table[initial]
SBIWA_C_FLAG_OFF
2
0
L_PROGNAME
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
L_FUNCTION /BIC/QIZL3_BW_SALES_ORD__10001
244425454354555444554545533333
F293F19AC3F27F31C53FF24FF10001
L_T_QRFCRCV Table IT_1936[1x56]
L_SUBRC 0
0000
0000
S_READ_ONLY
2
0
L_DELTA_TYPE E
4222
5000
RSAOT_C_DELTA-OWN E
4222
5000
SYST-REPID SAPLRSC1
5454554322222222222222222222222222222222
310C233100000000000000000000000000000000
RSAOT_C_DELTA-ALE A
4222
1000
L_NO_MORE_DATA
2
0
L_UPDMODE D
42
40
SBIWA_C_UPDMODE_DELTA D
42
40
RSAL_SAVE_SUBRC 0
0000
0000
L_POOLNAME %_T002T1
2553335322222222222222222222222222222222
5F40024100000000000000000000000000000000
S_S_ROIS-ISOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
G_FLAG_INTERFACE_INITIALIZED X
5
8
<%_TABLE_ROOSPRMSC> ???
%_SPACE
2
0
SYST ########################################
0000000000000000000000000000000000000000
000100000001000100000000000A000000000000
... + 40 ###############A#######P################
0000000000000004000000050000000000000001
0001000000010001000100000000000000000003
... + 80 ###################g####################
0000000000000000000600000000000000000000
0000000000000000000700000000000000000000
... + 120 #######################################T
0000000000000000000000000000000000010005
0000000000000000000000000000000000060004
... + 160 ################ u############# E0X X1
0000000000000001270000000000000222435253
00000000000000E0050020000C0000C000508081
... + 200 000 ####__S 001
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000010
... + 240 80
222223322222222
000008000000000
SBIW_C_TRUE X
5
8
SY-REPID SAPLRSC1
5454554322222222222222222222222222222222
310C233100000000000000000000000000000000
QS_NOSENDS NOSENDS
44544452
EF35E430
4 FORM DATA_TRANSFER
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7 128
SY-SUBRC 0
0000
0000
SY-REPID GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
4535355535544544443544355532222222222222
703A77AA11AC978E22802C544370000000000000
SPACE
2
0
SYST-REPID GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
4535355535544544443544355532222222222222
703A77AA11AC978E22802C544370000000000000
%_DUMMY$$
2222
0000
P_S_REQUEST-UPDMODE D
42
40
SBIWA_C_UPDMODE_DELTA D
42
40
SBIWA_C_UPDMODE_REPEAT R
52
20
SRSC_C_UPDMODE_INITSIMU S
52
30
SBIWA_C_UPDMODE_DELTAINIT C
42
30
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
L_FNAME RSC1_DELTA_BIW_GET
554354445454455445222222222222
2331F45C41F297F754000000000000
P_S_REQUEST-REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
RODKYF
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
22222222
00000000
L_T_ZL3_SALES Table IT_1926[0x103]
ROISGEN ZL3_BW_SALES_ORDER_ITEM PHD00
5435455544455454455454422222225443322222
AC3F27F31C53FF2452F945D00000000840000000
... + 40 PBW82 T /B
5453322222522222222222222222222222222224
02782000004000000000000000000000000000F2
... + 80 IC/CCPB0000000766 3Z7WZZ1QZLIW
4424454333333333322222222222353555355445
93F33020000000766000000000003A77AA11AC97
... + 120 HNBB8PBL5TTS7
4444354435553222222222222222222222222222
8E22802C54437000000000000000000000000000
... + 160 RFC_P92
2222222222222222222222222222222225445533
000000000000000000000000000000000263F092
... + 200 20060322161543 000000000
2222233333333333333222222222222333333333
0000020060322161543000000000000000000000
... + 240 00000
33333
00000
ROIST
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222
0000000000000000000000000000000
%_PRINT 001SBIE0001_RFC
2222333544433335544222222222222222222222
000000132950001F263000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 X8 ###A###PX_PAPER DRF
2222222225320004000555545452222222222454
000000000880000100008F010520000000000426
... + 120 C_P92 LIST1S
4553322222222222222222222222222222445535
3F09200000000000000000000000000000C93413
... + 160 TEXT 1 5D 2 ###Y
545522222222323422222222222222320015
4584000000001054000000000000002000E9
3 FUNCTION RSAP_DATA_TRANSFER
SAPLRSAP
LRSAPU06 137
I_ISOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
I_S_REQUEST REQU_43VWUSBH207E5H8W64KGNKSPNDZL3_BW_SA
5455533555544333434353344445544543545554
2515F436753282075588764B7EB30E4AC3F27F31
... + 40 LES_ORDER_ITEM 20061121210928RFC_B
4455454455454422222223333333333333354454
C53FF2452F945D000000020061121210928263F2
... + 80 W PHD00 PBW82 000000D T X
5222222544332222254533222223333334252252
7000000084000000002782000000000004040080
... + 120 X
5
8
I_T_SELECT Table IT_57[0x123]
RODIOBJCMP 0000
2222222222222222222222222222223333222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
22222222222222
00000000000000
L_S_LOGPARMS-MSGV3
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
RODCHA
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222Tell your basis guys
"ORA-01555: snapshot too old: rollback segment"
ie the job took too long for the current settings you have for rollbacks
They will adjust the settings -
Short dump when exporting to Excel
After installing SAP Gui 7.20, I get a short dump (Message_Type_x) whenever exporting a report to Excel (XXL).
SAP Gui 7.20
Patch level 5
Windows 7
Office 2010
has anybody run into this issue or know how to resolve it? Thank you.Hy,
I've the same problem, have you resolve it?
By,
Ale. -
Hi all
While doing MIGO for Delivery I am geeting a run time error, I am giving the details of the error below.
Runtime Errors MESSAGE_TYPE_X
Date and Time 05.11.2007 06:05:17
Short dump has not been completely stored (too big)
ShrtText
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Could not determine recipients for message type INVCON
Technical information about the message:
Diagnosis
An IDoc of message type INVCON was passed to the ALE layer, but the
three receiver fields in the header record were not filled. In this
case the ALE layer tries to determine the receivers from the
entries in the distribution model. There are no entries available
in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message
type or deactivate distribution for these message types.
Message classe...... "B1"
Number.............. 003
Variable 1.......... "INVCON"
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
gger Location of Runtime Error
Program SAPLMBWL
Include LMBWLU21
Row 53
Module type (FUNCTION)
Module Name MB_POST_GOODS_MOVEMENT
rce Code Extract
e SourceCde
23 ENDIF.
24 xcommit = x. "Performance
25 IF NOT xblnr_sd IS INITIAL.
26 xmkpf-xblnr = xblnr_sd.
27 MODIFY xmkpf INDEX 1.
28 * when a goods movement for an inbound or outbound delivery is posted
29 * directly from VL31N/ VL01N, XBLNR is not yet known when we call
30 * CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
31 * BKPF as well. There is no other way to forward XBLNR to FI as not
32 * every document is posted by MB_CREATE -> a new function module in
33 * MBWL for transferring the information, called by FI, meant to load
34 * the complete function group for all MBxx postings when this isn't
35 * required (Performance). Would be the better way to transport the
36 * information after switching off MBxx in later release.
37 * corresponding IMPORT ... FROM MEMORY ... can be found in
38 * AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
39 l_mem_id = 'MKPF-XBLNR'. " 641365
40 EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365
41 ENDIF.
42 IF xmkpf-xabln IS INITIAL. "note 434093
43 CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093
44 ENDIF. "note 434093
45 CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
46 EXCEPTIONS error_message = 4.
47 * As soon as we have started to put things into UPDATE TASK, we must
48 * ensure that errors definitely terminate the transaction.
49 * MESSAGE A is not sufficient because it can be catched from
50 * external callers which COMMIT WORK afterwards, resulting in
51 * incomplete updates. Read note 385830 for the full story.
52 IF NOT sy-subrc IS INITIAL.
>>> MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830
54 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
55 * MESSAGE A263.
56 ENDIF.
The programme was terminated in line 53 where there was a note 385830, I am trying to apply note 556000, is this the right approach.
Please guide me.
Sureshhi ,
the dump is correct . becuase of inconsistency system going to dump.
Put a break point at below FM and debug the FM and find out why sy-subrc eq 4 and where it is happenning. The reason for dump is not because of ABAP it is because of the Wrong functional process(some where in Config).
CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
EXCEPTIONS
error_message = 4.
IF NOT sy-subrc IS INITIAL.( other than 0 goes to dump)
MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830
sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
MESSAGE A263.
ENDIF. -
ALE using HRMDA message type - Comit not perform in receiving system
Hi,
I want to use ALE to transfer HR master data between two ECC instances. I have set-up all the configuration; distribution profile, filter etc... I tried to transfer the master data using standard SAP report RHALEINI.
The iDoc is generated and transfer correctly in the receiving system. The final status of the iDoc is 53 - Application document posted. The issue we have is that the comit to tables is not happening. Infotypes remains empty even if the status of the iDoc says it was posted. We are trying to transfer infotype 0000, 0002, 0001 and 0006
Anyone can help ?....
Thanks
LouisHi Ted,
Thanks for your answer,
Autorization is the first thing that we consider. We generate the IDOC by the program RBDMIDOC .
The job's user is the sap_all authorization. So it should not related with auth.
And this does not always occur. For example, two days ago it occurs, but today does not occur.
Best Regards
Hasan. -
Data transfer using ALE/IDOC into XML.
Dear All,
I have to transfer FI document data (FB01) from the sap system ,convert it into XML and dump it in 1 of the file servers.I want to do this using ALE/IDOC.Is it possible to do the same and how.Similarly i want to do the same for Vendor and Customer master i.e sending the data in XML format.
Kindly Suggest how do i go about doin the same..Its very urgent.Please help.
Thanks & Regards,
Lailu Philip.In continuation:
Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
Working ALE environment - See ALE Basis Configuration Guide;
ALE scenario design together with the business requirement;
Development access; and
ALE configuration access.
NOTES:
1. All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2. This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3. Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2. OUTBOUND PROCESSING
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV P&S - Segment 1
Segment fields
LIFNR Vendor account number
XBLNR Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
Click on ZINVRV01 and then on the Create icon
Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), 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, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR 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 new 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
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
Choose Create logical message type by double clicking on it
Click on change icon to enter change mode
Click on New entries to add a new type
Enter the required message type, in our case it is ZINVRV and an appropriate description
Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
Type in your message type ZINVRV and press enter
Click on New entries
Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
Choose the receiving systems to which the sending system must forward message type ZINVRV to.
For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
Make the settings for the communication with the other decentral systems, you have not set them yet.
Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
Create the output partner profile.
Distribute the customer model
Specify the name of the customer model.
You must specify the target system to which you want to distribute the customer model.
You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
The customer model must be maintained.
RFC destinations must be maintained.
The customer model must be distributed.
To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1. Example code
The code displayed below does the following:
populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
populates the control record info with the message type and IDoc type; and
calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
Data declaration statements
DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
Z1INVRV LIKE Z1INVRV,
C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR. Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR. Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. Segment name
IDOC_DATA-SDATA = Z1INVRV. Segment data
APPEND IDOC_DATA. Populate IDoc internal table
Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = IDOC_DATA
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3. INBOUND PROCESSING
3.1. Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters Reference field Opt Y/N
INPUT_METHOD BDWFAP_PAR-INPUTMETHD N
MASS_PROCESSING BDWFAP_PAR-MASS_PROC N
Export Parameters Reference field Opt Y/N
WORKFLOW_RESULT BDWFAP_PAR-RESULT N
APPLICATION_VARIABLE BDWFAP_PAR-APPL_VAR N
IN_UPDATE_TASK BDWFAP_PAR-UPDATETASK N
CALL_TRANSACTION_DONE BDWFAP_PAR-CALLTRANS N
Table Parameters Reference field Optional Y/N
IDOC_CONTRL EDIDC
IDOC_DATA EDIDD
IDOC_STATUS BDIDOCSTAT
RETURN_VARIABLES BDWFRETVAR
SERIALIZATION_INFO BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
populates a BDC table with the IDoc info;
calls the transaction via a BDC call; and
updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
WHEN C_SEGNAM.
Here we get the info from the idoc table
IT_Z1INVRV = IDOC_DATA-SDATA.
ENDCASE.
PERFORM REV_INV.
ENDLOOP.
PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV "Reverse invoice form
Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR. "Billing document number
APPEND BDC_TAB.
OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = 'ZINVRV'
USER = C_ALE_USER
KEEP = 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = C_TCODE
TABLES
DYNPROTAB = BDC_TAB.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
ELSE. "No problems
C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
Select from the sales document table to get user status number
SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
POSNR = VBRP-AUPOS.
Select from the status table to change the user status to pending
SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
STAT LIKE C_USER_STATUS.
IF JEST-STAT = C_US_PENDING. "User status is pending
JEST-INACT = C_UNCHECKED. "Make pending the active status
UPDATE JEST.
C_EXISTS = 'Y'. "I.E. An entry is already in table
ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
JEST-INACT = C_CHECKED. "Make everything else inactive
UPDATE JEST.
ENDIF.
ENDSELECT.
IF C_EXISTS = 'N'. "I.E. Pending has never been a status before
JEST-OBJNR = VBAP-OBJNR.
JEST-STAT = C_US_PENDING.
JEST-INACT = C_UNCHECKED. "Make pending the active status
INSERT JEST.
ENDIF.
ENDSELECT. "Select from VBRP (Billing document table)
ENDIF.
ENDFORM. " REV_INV
FORM UPDATE_IDOC_STATUS.
Now we check the CALL TRANSACTION return code and set IDOC status
CLEAR IDOC_STATUS.
IF RETURN_CODE = 0.
WORKFLOW_RESULT = '0'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '53'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ELSE.
WORKFLOW_RESULT = '99999'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM. " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1. Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2. Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1. Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Select an entry (EG. IDOC_INPUT_ORDERS) and copy
Type in module name Z_IDOC_INPUT_ZINVRV
Type in basic IDoc type as ZINVRV01
Type in message type as ZINVRV
Type object type as IDOCINVOIC (Invoice document) - Used for workflow
Direction should be set to 2 for inbound
Enter and save
3.2.2. Define FM settings (BD51) Client independent
Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
Click on New entries
Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
Enter 0 for mass processing in the output column
Save and Exit
3.2.3. Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
Log on to the appropriate receiving system client
Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
Choose Inbound with ALE service
Choose Processing with function module
Click on Processing with function module and choose create icon
Click on New Entries
Type in process code ZINR and give it a description and save
Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
Enter your process code ZINR
Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
Enter IDPKFIDCMT in object type
Enter MASSINPUTFINISHED in End event
Enter IDOCINVOIC in IDoc object type
Enter INPUTERROROCCURREDFI in IDoc start event
Enter INPUTFINISHEDFI in IDoc End event
Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3. Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1. Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
Add the message type ZINVRV with process code ZINR.
Enter the output mode (background, immediately) for inbound processing and NO message code.
Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4. Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
Hope this will help you,
If you want me to explain more, you can give me your email id.
Reward with points incase you are satisfied.
Regards,
Sushama -
IDoc to File, SM58 shows error, ST22 short dump - Runtime error
Hi friends,
I am doing a simple IDoc to file scenario using the EVMSTA01 IDoc. My XI is running on client 100 and I am trying to send the IDoc from the client 200 on the same machine. I have completed the design and configuration steps required and also performed the required steps in Sender client (Sm59, we21 and BD54) and receiver client (Sm59, IDX1 and IDX2).
When I tried sending the IDoc from WE19, status meesage says that, the IDoc has been successfully sent to the receiver but SM58 shows error "IDOC_ERROR_WORKFLOW_START_R". When I looked in to ST22, there was a short dump with the below message -
Runtime Errors MESSAGE_TYPE_X
Date and Time 18.10.2008 23:24:29
ShrtText
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Unable to read RFC destination WORKFLOW_LOCAL_200
Technical information about the message:
Message classe...... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_200"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
Trigger Location of Runtime Error
Program CL_SWF_RUN_WIM_LOCAL==========CP
Include CL_SWF_RUN_WIM_LOCAL==========CM07Z
Row 10
Module type (METHOD)
Module Name IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
rce Code Extract
e SourceCde
1 METHOD if_swf_run_wim_utl_internal~get_system_user .
2 DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4 TRY.
5 IF me->m_int_state-system_user IS INITIAL.
6 me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7 ENDIF.
8 re_user = me->m_int_state-system_user.
9 CATCH cx_swf_run_wim INTO l_excp.
>> MESSAGE ID l_excp->t100_msg-msgid
11 TYPE 'X'
12 NUMBER l_excp->t100_msg-msgno
13 WITH l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14 l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15 ENDTRY.
16
17 ENDMETHOD. "
Any help would be appreciated..!!
PS: Points would be assigned to all the helpful replys without failHi,
See check for RFC destination and it is working as per your configuration or not , i mean , it is trying to locate remote server.. , so try to check in sm59, remote login and the respective result is going to your required client or not ??
Also see the further errors while doing Idoc related scenarios..
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idocs not reaching XI . Not posted in the receiver SAP
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
Regards
Chilla -
Hi friends need some help in ALE IDOC !
For training purpose I am trying to create an IDOC using ALE
where I am using the same client as server as well as receiver......So I am using as receiver "NONE" . this is already present in the SM59 under logical systems..
But i cant create a port for that...as its saying its not compatible with the TRFC "
Can any one tell me what is the way to create the port ?Hi,
You are new to ALE and IDOCs so I am giving all step by step to do the ALE.
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Thanks
Sarada -
Hi,
Iam trying to send a MATMAS Idoc from one client to another client , which is in the same R/3. The outbound staus is 03 and the inbound is 51.
I just created a material (Material details are attached below for reference) and send tht material to the other client using BD10.
can you please tell me the Inbound function module name which i should use to post it again.
Material Name:KRMATERIAL
Industry sector : Mechanical Engineering
Material Type : Finished Products.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
Thanks
-KarthikHi Karthik,
Just follow the procedure, this is for MATMAS
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
<b>Reward Points if this helps,</b>
Satish -
what r the diffrent methods& steps to tranfer the data from outbound to inbound ,viceversa in ale/idoc ?
explain each and every method ? plzzzApplication Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User: MMUSER200 (This is the logon for dist.)
Client : 200
Password: MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as LGMODEL.
Sender as LG100.
Receiver as LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as LGMODEL.
Sender as LG200.
Receiver as LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as Mechanical Engineering
Material Type as Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time: WE07.
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
idoc:
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
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
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Create Model View
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD64 - Distribute the Model view
Message Type MATMAS
Tcode BD10 - Send Material Data
Tcode WE05 - Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 - Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Create Model View
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD64 - Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 - Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 - Send Material Data
Tcode WE05 - Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Check these step-by-step links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985
Reward points.. -
5 IDOC with status 29 Error in ALE service
hi there,
im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
IDOC Status Outbox:
IDOC failure between 13/07/2008 to 14/07/2009
1 IDOC with status 02 Error passing data to port
5 IDOC with status 29 Error in ALE service
IDOC Status InBox:
88 IDOC with status 51 Application document not posted
regards
rajuHi,
Check this thread.
DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Regards. -
Hi Friends,
Plz any one can give the brief step by step ALE , EDI, IDOC
I don't need the screen shots just sequence of transactions .
Please do this favor for me from long time am struggling with this.
thanks in Advance,
Sheethal.Jagadesh,
Go thru thesee.......
ALE---IDOC Creation Steps
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
check the following Links
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
ALE and IDOCs
iDocs
IDOCs !!!!!! need your help
idocs
ALE, EDI and IDOCS
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
Regards. -
Dump error during CK24 - SAPSQL_ARRAY_INSERT_DUPREC
Hi SAP Gurus,
i am facing problem during the material updation (T.Code CK24). before that i have done the material cost estimation then try to update material master by using t.code CK24. the following dump error occurs:
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Except. CX_SY_OPEN_SQL_DB
Date and Time 19.06.2008 11:05:00
Short text
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKAUP" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "INSERT_TABLES" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
Missing RAISING Clause in Interface
Program SAPLKAUP
Include LKAUPF01
Row 397
Module type (FORM)
Module Name INSERT_TABLES
Trigger Location of Exception
Program SAPLKAUP
Include LKAUPF01
Row 464
Module type (FORM)
Module Name INSERT_TABLES
Source Code Extract
Line
SourceCde
434
ENDIF.
435
Do not write empty CO document headers for parked documents!!
436
--> ugly coding but it looks like that "empty" headers are
437
possible in some circumstances
438
IF GD_PARKED_DOCUMENT = 'X' AND
439
COBK_INS-SUMBZ = 0 AND
440
COBK_INS-ALEBZ = 0.
441
DELETE COBK_INS.
442
CONTINUE.
443
ENDIF.
444
DELBZ setzen
445
COBK_INS-DELBZ = 0.
446
CPUDT/CPUTM setzen
447
IF COBK_INS-CPUDT IS INITIAL
448
OR COBK_INS-CPUTM IS INITIAL.
449
COBK_INS-CPUDT = SY-DATUM.
450
COBK_INS-CPUTM = SY-UZEIT.
451
ENDIF.
452
TIMESTMP setzen
453
IF COBK_INS-TIMESTMP IS INITIAL.
454
COBK_INS-TIMESTMP = GD_TIMESTMP.
455
ENDIF.
456
USNAM setzen
457
IF COBK_INS-USNAM IS INITIAL.
458
COBK_INS-USNAM = SY-UNAME.
459
ENDIF.
460
Aenderungen merken
461
MODIFY COBK_INS.
462
ENDLOOP.
463
.....COBK verbuchen...................................................
|>>>>>| INSERT COBK FROM TABLE COBK_INS. |
465
noch kein REFRESH fuer COBK_INS -> wird noch fuer ALE gebraucht
466
ENDIF.
467
468
.....ggf. Einzelposten versenden......................................
469
IF NOT ALE[] IS INITIAL.
470
LOOP AT ALE.
471
PERFORM SEND_DOCUMENT USING ALE-KOKRS ALE-BELNR ALE-LOGSYSO.
472
--> COBK_INS, COEP_INS und COEPL_INS werden hier gebraucht!
473
ENDLOOP.
474
REFRESH ALE.
475
ENDIF.
476
477
.....COEP verbuchen...................................................
478
IF NOT COEP_INS[] IS INITIAL AND GB_LATE_COEP_INS <> ON.
479
INSERT COEP FROM TABLE COEP_INS.
480
REFRESH COEP_INS. "REFRESH wird in UPDATE_TABLES gemacht!
481
ENDIF.
482
483
.....COEPL verbuchen..................................................
please help me to overcome this problem.
point will be rewarded
Than'x
DhananjayHi,
Please provide me the solution for the above issue , I am also facing the same, what excatly is the remedy for this.
regards
Ritesh
Maybe you are looking for
-
How can i get apps from my itunes to my iphone?
okayy so i want to get the facebook application on my iphone and i dont have the app store on my ipone.. soo how can i get the app from itunes to my phone for ffree? i have a windows computer and i have restrictions on my phone because i use it too m
-
I'm praying somebody here has an idea to help me. iCloud has suddenly gone nuts on my iMac. It works only when it wants to work and then stops for no reason. When it stops I am no longer able to click the mail icon and open any mail even the old stuf
-
Adding additioanl field to report in KSB1
Hi, My requirement is to add field BSEG-ZUONR to the report in KSB1. I've apply ossnote 325546 and 359691. But the output is still not coming out. The report is not shoing the column BSEG-ZUONR The sap system has upgraded to release 700. Does a
-
Hi, Please note that we had implemented a note 638097 for derivation rule for distribution channel at sales order level. SAP had suggested that this may throw an error KE396 and we will have to implement other note to suppress.However even after impl
-
Hie,I recently bought iphone5 in spore but I am going to china next week, can I use my iPhone in china with china SIM card? iPhone 5 is not released in china yet.