RFC Destination to test EDI outbound process
Hi,
I am configuring RFC Destination. SAP provides a tool to test EDI outbound process even when EDI subsystem is not actually connected. Do you know what the RFC destination settings should be in this scenario? Thank you.
Hi,
Please check this links perhaps they may help.
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/mysap3/sap109.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm
Regards,
Ferry Lianto
Similar Messages
-
An RFC destination could not be specified for the logical system
Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
KhushbooHi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo -
Hi
I have 75+ idoc interfaces. some are high priority interfaces and some are low priority interfaces.
We did queue prioritization for those interfaces too....But we have only one RFC destination for
all the interfaces.
We are thinking to go for one more RFC destination(SM59), so that we can route low priority high volume
load through this. This way high priority messages can't be effected.
Is this the right approach of implementing ?
thanks
kumar>If it is outbound idoc (ECC-xi-third party), then workprocesses of ECC will be consumed right ? and not XI ? Plz correct me if I am wrong.
Both WP will be used on ECC and XI
>If we have only one RFC destination:
>
>1. out of 75+ interfaces, e.g if one high volume-low priority interface triggers 10k idocs and after
>that if high priority interace get triggers, then first high volume-low priority messages will be piled up
>in RFC destination and after they get processed then only high priority messages will ger process.
>If We have 2 RFC destination:
>
>2. we can route high volume-low priority interface into one RFC destination and high priority interface
>into another RFC destination. This way high priority interfaces won't be effected
If both RFC destinations point to the same logon group, WP's to be consumed will be taken from the same "pool" so I see no benefit in separating RFC destinations, it's the same of using a single RFC destination.
If you use different logon group then it's different, because you can assing more resources to a logon group than to another (this means different number of WPs) and at the end different priority.
Regards,
Sergio -
RFC For IDoc outbound processing
I am creating an RFC for BDC for call transaction we19
input as : idoc number
and output:-.. iDoc Outbound processing done
so:-
I go to we19> give iDoc Number (say, some number for ALEREQ01), and execute> click on Outbound processing-->click enter -->enter
in this way, I can process any iDoc from SAP system to outbound.
I want to create RFC for the same.
Problem:-
when i am executing that RFC, and when I check the iDoc status in we05, that iDoc shows status as Idoc ready to dispatch( its in yellow color).. Its not showing green color and not saying that IDoc passed OK
when I try manually ,I see the status green..OK..successfully
Any idea why I am getting this problem??
Is there any problem in my BDC recording?..but when I run that recording for Process, i dont see any problem,it executes successfully.. but when I copy the Code from BDC and make a RFC using that code, its giving problem as mentioned.Hi Ankit,
Theorotically it should work.... but I'll suggest not to use BDC here. What you can do is,
1. You have Idoc number..Right?
2. Read control record from EDIDC and data record from EDID4.
3. Then call Master_idoc_distribute.
4. This will again distribute the same IDoc with same control and data record as a new one. It will be same as WE19 , but without WE19.
Please check and confirm.
Regards,
Audy. -
Is there FM to Test a RFC Destination?
Hi Ruben,
SM59 is the transaction to test for RFC destination.
Just click on REMOTELOGON button. It will open destination system logon.
The function module <b>/SDF/SL_RFC_GET_CLIENT_REMOTE</b> will determine the RFC destination.
The function module <b>ARFC_DEST_CONFIRM</b> will confirms destionation of RFC.
The function module <b>RFC_CHECK_DESTINATION</b> will check the destionation of RFC.
Thanks,
Vinay -
AES filing error - Idoc Outbound Processing: EDI number cannot be compiled
Hi Gurus,
We are configuring the AES filing.
we've done the EDI configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha -
Hi All,
I am new to ALE. I want to know what is the actual process behid inboud and outbound services in ALE.Hi,
1.Here out bound means sender.Inbound mens --receiver.
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.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Regards,
Shiva. -
EDI Outbound file trigger not happening automatically.unix script
EDI OUT bound issue:-
We are processing IDOC by using WE19 -> Here we are selecting existing IDOC -> By using pushbutton Start Outbound Processing the IDOC EDI file is creating in directory with file name as:- /abc/xyz/edi/DECVDE_989898.
In the same directory we have unix script file push_idoc_sci.sh is available which sends this EDI file to unix server.This script is working fine when we do manual sending of edi file - there is no issue in the script.
1> We configured the port SAPEDI which sends this EDI file automatically by using this script file. But this is not happening.
WE21 settings:-
Outbound file TAB:- Phycal directory -> /abc/xyz/edi/
Function module: EDI_PATH_CREATE_MESTYP_DOCNUM
Outbound Trigget TAB:-
Automatic Start Possible check box checked.
RFC destination -- SERVER_EXCE.
Directory-- /abc/xyz/edi/
Command file -- push_idoc_sci.sh
Inbound file TAB:- Phycal directory -> /abc/xyz/edi/ in
FM -- EDI_PATH_CREATE_CLIENT_DOCNUM
2> RFC destination TCP/IP connections:- SERVER_EXEC configured with parameters:
Application server :- Program: rfcexec.
The Issues is EDI file is creating in applicastion server, but it is not going automatically to unix server as automated process. even we mentoned the script in port defination to send automatically.
Is there any we are missing? any seetings do we need to do extra?
Please let us know.
Thanks in advance.
Sreedhara.Hi Hi sreedhara gupta
what REDDY said is correct. Still you if you want test by using WE19 ....Put break point at include MSED7F03 at IF direction_in <> c_direct_incoming.
change the value of control_record_in-outmod to 1 or 3.
Note: Imp thing is............. there is a chase of missing segments which are requied in EDI Subsystem.
Thanks
Ramesh
Edited by: Ramesh on Mar 26, 2010 7:07 PM -
Error on outbound processing (- to IDoc), nodetailed error message
Hi guys!
I'm facing a problem with sending IDocs to R/3. My messages have red flag in outbound status, but there is no detailed error message. Everything seems to be ok, but my IDoc doesn't arrive to R/3 and there is that red flag in XI.
What could cause this? It seems like there is some communication problem. Any ideas?
Thank you,
OlianHi,
IT will give the status number,what is the status number in IDOC check it and update the thread.
if u find its a data problem u can debugg the FM,go to WE19 and give ur IDOC number and there u will find the option start out bound processing form this opion u can debugg the code and know wat is the error.
Check ur ALE settings.
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Regards,
Phani
Reward points if Helpful -
Hi Experts,
I am doing User Exit for MIGO.
I have done it successfully.but problem comes when the email is sent to the vendor, MIGO is getting DUMP.
So, to cross check i have remove the User Exit of MIGO. but to my surprise when i press POST button in MIGO the similiar DUMP comes.
So wht is the solution for this.
For your Information DUMP message is:
Runtime Errors MESSAGE_TYPE_X
Date and Time 06.12.2007 14:57:55
Short text
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).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
No RFC destination is defined for SAP Global Trade Services
Long text of error message:
Technical information about the message:
Message class....... "/SAPSLL/PLUGINR3"
Number.............. 002
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLMBWL" or "LMBWLU21"
"MB_POST_GOODS_MOVEMENT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "vngsap1"
Network address...... "192.168.0.10"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "VNGSAP1"
Database type..... "MSSQL"
Database name..... "EC6"
Database user ID.. "ec6"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 20 2007 00:45:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 102
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 21953056
Heap.... 0
Page.... 73728
MM Used. 15443024
MM Free. 1280936
User and Transaction
Client.............. 800
User................ "VEDHRUV"
Language key........ "E"
Transaction......... "MIGO "
Transactions ID..... " "
Program............. "SAPLMBWL"
Screen.............. "SAPLMIGO 0001"
Screen line......... 18
Information on where terminated
Termination occurred in the ABAP program "SAPLMBWL" - in
"MB_POST_GOODS_MOVEMENT".
The main program was "SAPLMIGO ".
In the source code you have the termination point in line 59
of the (Include) program "LMBWLU21".
Source Code Extract
Line
SourceCde
29
when a goods movement for an inbound or outbound delivery is posted
30
directly from VL31N/ VL01N, XBLNR is not yet known when we call
31
CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
32
BKPF as well. There is no other way to forward XBLNR to FI as not
33
every document is posted by MB_CREATE -> a new function module in
34
MBWL for transferring the information, called by FI, meant to load
35
the complete function group for all MBxx postings when this isn't
36
required (Performance). Would be the better way to transport the
37
information after switching off MBxx in later release.
38
corresponding IMPORT ... FROM MEMORY ... can be found in
39
AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
40
l_mem_id = 'MKPF-XBLNR'. " 641365
41
EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365
42
ENDIF.
43
IF xmkpf-xabln IS INITIAL. "note 434093
44
CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093
45
ENDIF. "note 434093
46
47
ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49
ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50
CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51
EXCEPTIONS
52
error_message = 4.
53
As soon as we have started to put things into UPDATE TASK, we must
54
ensure that errors definitely terminate the transaction.
55
MESSAGE A is not sufficient because it can be catched from
56
external callers which COMMIT WORK afterwards, resulting in
57
incomplete updates. Read note 385830 for the full story.
58
IF NOT sy-subrc IS INITIAL.
>>>>>
MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830
60
sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61
MESSAGE A263.
62
ENDIF.
63
Optische Archivierung
64
Spaete Erfassung mit Barcode
65
Redesign of barcode handling -> note 780365
66
PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
67
xmkpf-mjahr
68
barcode.
69
70
MOVE-CORRESPONDING xmkpf TO emkpf.
71
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
72
EXCEPTIONS
73
error_message = 4.
74
MOVE-CORRESPONDING xmkpf TO emkpf.
75
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
76
EXCEPTIONS
77
error_message = 4.
78
IF NOT sy-subrc IS INITIAL.
Contents of system fields
Name
Val.
SY-SUBRC
4
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
MIGO_STATUS
SY-UCOMM
OK_POST1
SY-TITLE
Goods Receipt Purchase Order 4500017132 - shah
SY-MSGTY
X
SY-MSGID
/SAPSLL/PLUGINR3
SY-MSGNO
002
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20071206
SY-UZEIT
145755
SY-XPROG
SAPLBPFC
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
7 FUNCTION SAPLMBWL LMBWLU21 59
MB_POST_GOODS_MOVEMENT
6 METHOD SAPLMIGO LMIGOKG1 921
LCL_MIGO_KERNEL=>GOODS_MOVEMENT_POST
5 METHOD SAPLMIGO LMIGOKD1 309
LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
4 METHOD SAPLMIGO LMIGOKD1 9
LCL_MIGO_KERNEL=>DOCUMENT_POST
3 METHOD SAPLMIGO LMIGOST2 124
LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER
2 METHOD SAPLMIGO LMIGOFR2 172
LCL_MIGO_FRAME=>OKCODE_DISPATCH
1 MODULE (PAI) SAPLMIGO LMIGOPAI 11
PAI_OKCODE_DISPATCH
Chosen variables
Name
Val.
No. 7 Ty. FUNCTION
Name MB_POST_GOODS_MOVEMENT
XBLNR_SD
2222
0000
0000
0000
EMKPF
000000000000000000 ##
2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XMSSA[]
Table IT_3831[0x196]
FUNCTION-POOL=MBWLDATA=XMSSA[]
Table reference: 396
TABH+ 0(20) = 0000000088F26C31000000008C010000F70E0000
TABH+ 20(20) = 00000000C4000000FFFFFFFF04E90400E01B0000
TABH+ 40( 8) = 08000000C1108001
store = 0x00000000
ext1 = 0x88F26C31
shmId = 0 (0x00000000)
id = 396 (0x8C010000)
label = 3831 (0xF70E0000)
fill = 0 (0x00000000)
leng = 196 (0xC4000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000134
occu = 8 (0x08000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0x40F26C31
>>>>> 2nd level extension part <<<<<
tabhBack = 0xA0F5EA30
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
RRESWK
22222222222
00000000000
00000000000
00000000000
%_SPACE
2
0
0
0
L_MEM_ID
2222222222
0000000000
0000000000
0000000000
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
XMSPR_KEY
00000000
222222222222222222222222222222222222233333333
000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000
SCREEN
GODYNPRO-DETAIL_TAKE
4445455424454445544422222222222222222222222222222222222222222222222222222222222222222222222222
7F49E02FD45419CF41B500000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IT_RSTRUCT
Table[initial]
XMKPF-XABLN
2222222222
0000000000
0000000000
0000000000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
SAPLMBWL
5454445422222222222222222222222222222222
310CD27C00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ODM07M[]
Table[initial]
GT_GOCOMP
000000000000 #### 00000000000000
3333333333332222222222222222222222222222222222222222222220000222222222222223333333333333322222
000000000000000000000000000000000000000000000000000000000000C000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
4
0000
4000
L_ATPCB
22222
00000
00000
00000
XMKPF-MBLNR
5000011865
3333333333
5000011865
0000000000
0000000000
XMKPF-MJAHR
2007
3333
2007
0000
0000
BARCODE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T003
800WE50AMS X XX XXXXXH
3335433445222222222522222222222222225522555554222222
80075501D3000000000800000000000000008800888888000000
0000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000
KNVV
00000000 000
2222222222222222222222222222222223333333322222222222222222222233322222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T064B
2222222222222222222222
0000000000000000000000
0000000000000000000000
0000000000000000000000
VGMSEG[]
Table[initial]
No. 6 Ty. METHOD
Name LCL_MIGO_KERNEL=>GOODS_MOVEMENT_POST
ES_EMKPF_OLD
5000011865200700000000000000 ##
3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
5000011865200700000000000000000000000010000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
SAPLMIGO
5454444422222222222222222222222222222222
310CD97F00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_EMKPF
000000000000000000 ##
2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OREF_TITLEBAR
|
| E0001000 |
| 60009000 |
| LS_EMKPF-SUBRC |
| 0 |
| 0000 |
| 0000 |
| C_MOD_ON |
| 1 |
| 3 |
| 1 |
| 0 |
| 0 |
| GOITEM-ERFMG |
| 0.0.0.0.0.0.1. |
| 0001000 |
| 000000C |
| LS_EMKPF-MBLNR |
| |
| 2222222222 |
| 0000000000 |
| 0000000000 |
| 0000000000 |
| SY-XPROG |
| SAPLBPFC |
| 5454454422222222222222222222222222222222 |
| 310C206300000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-REPID |
| SAPLMIGO |
| 5454444422222222222222222222222222222222 |
| 310CD97F00000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-MSGID |
| /SAPSLL/PLUGINR3 |
| 25455442545444532222 |
| F3103CCF0C579E230000 |
| 00000000000000000000 |
| 00000000000000000000 |
| TV_GODEFAULT_TRANSFER-CX |
| <initial> |
| <initial> |
| <initial> |
| SPACE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| SY-MSGNO |
| 002 |
| 333 |
| 002 |
| 000 |
| 000 |
| SY-MSGV1 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| ES_EMKPF_OLD-MSGV1 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| SY-MSGV2 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| SY-MSGV3 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| SY-MSGV4 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| GODEFAULT_TV |
| 101 GR goods receipt |
| 2222223332245266667276666772222 |
| 000000101007207FF43025359040000 |
| 0000000000000000000000000000000 |
| 0000000000000000000000000000000 |
| LS_EMKPF-MJAHR |
| 0000 |
| 3333 |
| 0000 |
| 0000 |
| 0000 |
| OREF_TIP |
|
D0002000
90006000
TV_GOSPLIT-CURRENT_LINE
<initial>
<initial>
<initial>
No. 5 Ty. METHOD
Name LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
I_SIMULATE
2
0
0
0
I_SIM_VALUES
2
0
0
0
I_ERROR_ONLY
2
0
0
0
E_OK
2
0
0
0
ET_XMSEG
Table[initial]
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
LS_EMKPF
5000011865200700000000000000 ##
3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
5000011865200700000000000000000000000010000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LT_EMSEG
Table IT_4407[2x744]
FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_EMSEG
Table reference: 460
TABH+ 0(20) = F06C0731F83FE73000000000CC01000037110000
TABH+ 20(20) = 02000000E8020000FFFFFFFF0400000040420100
TABH+ 40( 8) = 10000000C1308001
store = 0xF06C0731
ext1 = 0xF83FE730
shmId = 0 (0x00000000)
id = 460 (0xCC010000)
label = 4407 (0x37110000)
fill = 2 (0x02000000)
leng = 744 (0xE8020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#001704
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xB8902E31
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 3425 (0x610D0000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0xE0D66931
>>>>> 2nd level extension part <<<<<
tabhBack = 0x00F11C31
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
LT_XMSEG
Table IT_4408[2x2364]
FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_XMSEG
Table reference: 464
TABH+ 0(20) = A0BEF93070D7693100000000D001000038110000
TABH+ 20(20) = 020000003C090000FFFFFFFF0400000030310100
TABH+ 40( 8) = 04000000C1308401
store = 0xA0BEF930
ext1 = 0x70D76931
shmId = 0 (0x00000000)
id = 464 (0xD0010000)
label = 4408 (0x38110000)
fill = 2 (0x02000000)
leng = 2364 (0x3C090000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#001613
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x28DF3031
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 3511 (0xB70D0000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 4 (0x04000000)
lineAlloc = 4 (0x04000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0x28D76931
>>>>> 2nd level extension part <<<<<
tabhBack = 0x90F4EA30
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
LT_IMSEG
Table IT_4396[2x2792]
FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_IMSEG
Table reference: 465
TABH+ 0(20) = D0D5693190D7693100000000D10100002C110000
TABH+ 20(20) = 02000000E80A0000FFFFFFFF04000000E0410100
TABH+ 40( 8) = 04000000C1308001
store = 0xD0D56931
ext1 = 0x90D76931
shmId = 0 (0x00000000)
id = 465 (0xD1010000)
label = 4396 (0x2C110000)
fill = 2 (0x02000000)
leng = 2792 (0xE80A0000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#001702
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xE01BC930
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 3413 (0x550D0000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 4 (0x04000000)
lineAlloc = 4 (0x04000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0xC8626B31
collHook = 0x00000000
ext2 = 0x80626B31
>>>>> 2nd level extension part <<<<<
tabhBack = 0xD88C0331
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
LT_CANCEL
Table[initial]
ABAP_TRUE
X
5
8
0
0
LCL_MIGO_GLOBALS=>IF_BADI
|
| F0000000 |
| 70008000 |
| SYST |
| ######################################T##########################################ÿ##### C#### |
| 0000000000000000000000000000000000000050000000005000000000000000000000000000109000F00050240000 |
| 100010000000000000001000100010000000004000C0B0403000000000000000000000000000B00000F00080030400 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000 |
| 00000000000000000000000000000000000000000000000010000000000000000000000000000000000000D000000C |
| LS_XMKPF |
| 80050000118652007WEWEPR20071206200712062007120614575300000000VEDHRUV |
| 3333333333333333354545533333333333333333333333333333333333333544455522222222222222222222222222 |
| 8005000011865200775750220071206200712062007120614575300000000654825600000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| ME |
|
F0000000
D0002000
%_SPACE
2
0
0
0
L_NO_ITEMS
2
0
0
0
TV_GODEFAULT-CX
<initial>
<initial>
<initial>
LCL_MIGO_GLOBALS=>CALLER_SYTCODE
MIGO
44442222222222222222
D97F0000000000000000
00000000000000000000
00000000000000000000
LCL_MIGO_GLOBALS=>RETAIL_CONSIGNMENT_ACTIVE
2
0
0
0
%_FSREG_001
No. 4 Ty. METHOD
Name LCL_MIGO_KERNEL=>DOCUMENT_POST
E_OK
2
0
0
0
ME
|
| F0000000 |
| D0002000 |
| ABAP_FALSE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| LCL_MIGO_GLOBALS=>EXTERNAL_CALL_LEAVE_AFTER_POST |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 3 Ty. METHOD |
| Name LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER |
| I_OKCODE |
| OK_POST1 |
| 4455455322222222222222222222222222222222222222222222222222222222222222 |
| FBF0F34100000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000 |
| OREF_BADI_LOG |
|
D0002000
5000A000
%_FSREG_001
%_PRINT
000 0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LCL_MIGO_GLOBALS=>KERNEL
|
| F0000000 |
| D0002000 |
| %_VIASELSCR |
| # |
| 0 |
| 4 |
| OREF_DETAIL_BATCH |
|
60009000
0000F000
GOSEARCH_PO
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 2 Ty. METHOD
Name LCL_MIGO_FRAME=>OKCODE_DISPATCH
I_OKCODE
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
L_MSG_STRING
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_OKCODE
OK_POST1
4455455322222222222222222222222222222222222222222222222222222222222222
FBF0F341000000000000000000000000000000000000000000000000000000000Hi Dhruv Shah,
Can you please tell me which user exit you are using for doing that. coz i am in need of that.
Thanks,
Ajeeth -
Troubleshoot: How to process messages in "Recorded for Outbound processing"
Dear Experts,
I have File >XI(3.0)>IDoc scenario with 10-25 interfaces. Per interface an average of 200 msges.
Now we have an issue. from past 6 days all the messages for one of the interfaces are in status: "Recorded for Outbound processing"(with that single small black right arrow) in SXMB_MONI(around 1760 till now). Other than this few 100 messages for couple other interfaces are also in same status. There are other message interfaces using the same Idoc type; but they dont have this problem.
I have checked the queues: SMQ1/Q2. There are no errors. The other threads mention about some reports; but all are for error messages. So that also did not help!
On the first day someone had deleted the error queue entry. They had first checked the message in the queues but that was not showing any status. (This is very strange... but for some messages , the left most status column is not showing any status at all.. but while clicking on the end time column; I am getting the pop up which says succesfully processed). But this is not our problem right now.
Please help me process the messages in the "Recorded for Outbound processing" status.. some how!!!
Thanks in advance for your inputs....
P.N: Runtime workbench here is not configured properly. No CC monitoring tab; message monitoring shows only adapter messages etc.... So cannot check anything hereThank you for your inputs.
@Udo.... SMQR- no issues.
The RFC destination is fine.
@Abhishek The Idoc has not reached SAP. The xml messages in XI are in "Recorded for outbound processing" which is kinda like Scheduled, i think. Anyway I checked the R/3 cant find the messages or errors.
Any help would be highly appreciated.... -
RFC Destination not getting connected - IDoc to XI scenario
Hi Everybody,
I want send an IDoc from R/3 System to Xi, I have created Two logical systems (Sender and Receiver correspondingly) and i have assigned the clients to them.
Once i create RFC destination, i have specified all my technical settings as well as Login/Security settings, once i click, "Remote Log On" it takes me directly to Login page of XI. Please guide me how to solve the problem. If i click Test---> Authorization, it prompts out with an error "Name and Password is incorrect (repeat Logon)", but i have given exact username and password.
I am a fresher to XI.... please give me some documents related to IDoc to XI scenario step by step to [email protected] I would be grateful and appreciate you if u would help me to sort out this problem....
Please give me step by step solutions.... Thanks in Advance...
Regards/GuruRequirements in R3 system:
1. Create RFC destination pointing to XI in SM59
2. Create port for XI using we21
3. create Outbound Entry in partner Profile for XI in we20.
Requirements in XI system:
1. Create Technical System pointing to the R3 system.
2. create Business System pointing to the R3 system.
If you want to send IIDOC out of XI,
1. SM59 - Create RFC destination
2. IDX1 - Create port
3. IDX2 - Import Metadata.
Note:u dont need a IDOC sender adapter or a Sender Agreement to sent a IDOC to XI.
Check dis link for more info:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
please refer to michel book on IDCO usage in XI
Message was edited by:
Sreeram Reddy -
Help with RFC sender, Program And RFC Destination
Hi!!
my scenary is asynchronous
RFC Sender -> SAP-XI -> Oracle reciever
I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI receive the message but the message is empty.
1. In my program on the line
CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
2. I rewrite my program, that line to
CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
3. I rewrite my program, that line to
CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
What is my Error?
Where am i making a mistake?
RFC
FUNCTION zbapi_sd_ped_ord_servic.
*"Interfase local
*" TABLES
*" PED_ORDEN STRUCTURE ZSD_RFC_T04
*" RETURN STRUCTURE ZSD_RFC_R06
TABLES: zsd_ped_orden, zsd_rfc_r01.
DATA: tb_ped_orden LIKE zsd_ped_orden OCCURS 0 WITH HEADER LINE,
tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
*Get Pedido by Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
FROM zsd_ped_orden
WHERE estatus EQ space.
LOOP AT tb_ped_orden.
MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
APPEND ped_orden.
tb_ped_orden-estatus = 'X'.
tb_ped_orden-fecha_actualiz = sy-datum.
tb_ped_orden-hora_actualiz = sy-uzeit.
MODIFY tb_ped_orden.
ENDLOOP.
MODIFY zsd_ped_orden FROM TABLE tb_ped_orden.
COMMIT WORK.
*Errors in Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
FROM zsd_rfc_r01
WHERE estatus EQ space.
LOOP AT tb_rfc_orden_error.
MOVE-CORRESPONDING tb_rfc_orden_error TO return.
APPEND return.
tb_rfc_orden_error-estatus = 'X'.
tb_rfc_orden_error-fecha_actualiz = sy-datum.
tb_rfc_orden_error-hora_actualiz = sy-uzeit.
MODIFY tb_rfc_orden_error.
ENDLOOP.
MODIFY zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
COMMIT WORK.
ENDFUNCTION.
PROGRAM
REPORT ZBAPI_SD_PED_ORD_SERVIC.
DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
TABLES
ped_orden = ped_orden
return = return
EXCEPTIONS
communication_failure = 1
system_failure = 2
OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE 'error' type 'I'.
ENDIF.
COMMIT WORK.
RFC DESTINATION
RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
Connection TYpe: TCP/IP Connection
Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
Gateway host: host00
Gateway service: sapgw00hi
For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
a) RFC destination
b) RFC channel in the XI directory
This weblog is a response to a few question about the basic configuration of the RFC sender adapter
that were posted on the XI forum (and also on my e-mail)
So here we go, basically we have to configure 2 things:
a) RFC destination
b) RFC channel in the XI directory
RFC destination:
1. To create the RFC go to TCODE: SM59
2. Create new destination of type T (TCP/IP)
3. Make sure you select Registered Server Program option before writing your program ID
4. Write you program ID (remember it's case-sensitive)
5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
7. No configuration in the J2EE administrator nessecary
Now we can proceed to RFC channel configuration:
1. Enter your Application Server
2. Your Application Server Service
3. Enter your Program ID from the RFC destination
And we're done:)
Now you can test the RFC destination in SM59 to see if it works.
Please chk this following link.
1. RFC Processing with the RFC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
2. Configuring the Sender RFC Adapter -
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
3. /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
regards
Manas -
Scheduled for Outbound Processing in SXMB_MONI
I have a scenario RFC -> ccBpm1 -> ccBpm2 -> ccBpm3 -> RFC.
The scenario was working perfectly. I made some simple changes in ccBpm3 and some errors started to happen.
The Xml message from ccBpm1 to ccBpm2 started to stuck (message Scheduled for Outbound Processing in SXMB_MONI). I didn´t make ANY change in ccBpm1 or ccBpm2, before the error started.
When I made a "dummy" change in ccBpm2 and I reactivate it, the message from ccBpm1 to ccBpm2 process, but then the message from ccBpm2 to ccBpm3 stucks. If I do a dummy change in ccBpm3, the message from ccBpm1 to ccBpm2 stucks again.
I have no Queues locks in smq1 and smq2. The Cache status are all 0 in SXI_CACHE. I have tried to reimport all Integration Process in Integration Directory, but no sucess.
Seems to be any kind of bug.
Any idea?
ThanksFirst, I would like to know.. if there was a justification to divide the scenario into 3 BPMs. Because BPMs add to system performance. They get converted to workflows on abap engine and context switches from java to abap engine. You might want to check you configuration in ID test configuration and then close analysis of the message processing in each of the ccBPMs.
VJ -
Hi All,
I am doing IDoc to File scenario. I have my IDocs in AXI system and XI in ZXI system.I want to send idocs from AXI to ZXI. I have configured the following in AXI :
RFC dest to ZXI (Dest4ZXI)
Transaction Port to ZXI having RFC dest as Dest4ZXI
Logical system for receiver file system
Partner profile for receiver file system with outbound parameter
and the following configuration in ZXI:
RFC dest to AXI (AXICLNT100)
Port to get IDoc's metadata from AXI (SAPAXI) having RFC dest as AXICLNT100
In SLD, i created a tech sys and business sys for sender system AXI and then i created a scenario in ZXI for IDoc to File. In IR, imported the idoc and created all other objects till interface mapping. In ID, assigned the business system, created a service for file receiver and created rec det,int det and rec agreement.
Using Idoc test tool i started the outbound processing after giving the data and control record and got the IDoc sent successfully message.
Control record values:
Receiver: port = (port created in AXI), partner no = (LS File receiver sys created in AXI)
sender : port = (SAPAXI - port creted in zXI), partner no = (AXICLNT100 - LS created in sld - which is same name as RFC detination created in ZXI)
If i check in we05, its green flag. But in sm58, error status message for the idoc is showing as "No service for the system SAPAXI for client 100 in Integration Directory.
Note: I am using a custom IDoc with 8 fields.
Kindly reply if my descriptions are not clear!
Appreciating all help.
Thanks in advance,
UmaHi Uma,
<b>Have u imported the Business System as Service or not?create u r cc in the service for that bs only</b>
If not just try with it..
If the sender system is maintained as the business service then we have to edit adapter specific identifiers and give the appropriate logical system name in the integration directory...
In ID goto Service Adapter-Specific Identifiers and mention the Logicalsystem and Client and ID...
Check this blog
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
and also
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
for refernece...
Regards,
Sridhar
Maybe you are looking for
-
How can I find what time a tab was opened in Safari?
How can I find out what time a tab was opened in Safari?
-
Captivate 6 Slide Audio screen not displaying correctly
Upon trying to rerecord a slides's audio today this screen opened up - I could record, but not save because the save button is not displaying. I was able to record new audio on the same project on Friday. I tried deleting and recodring new audio an
-
I have a FLA that has a call to my remote server. When I select Debug Movie I always get the error dialog box that says that the Flash player has stopped a potentially unsafe operation and that it is trying to communicate with an internet location, t
-
i really need some advice of things that i could possibly do before i take it somewhere
-
My ultimate goal is to have an interactive form returned by email include the completed form with the data. I would prefer not to have only the data returned but I want the form to be returned (to [email protected]) already populated with the data fr