Auto Packing Message Type

Hello All,
I got a requirement for Auto-packing in outbound delivery via IDOC process.
Can anybody through some light on the above requirement in finding Message type, process code and so on...
your every suggestion or hint will help me to fulfill the requirement.
Thanks in advance.
Best Regards
Suresh.

Hi,
Auto Packing message type: SDPACK
Process code: SDPA
Basic type: SDPAID01
Regards
Suresh.

Similar Messages

Auto Packing in outbound delivery via IDOC

Hello All,
I got a requirement for Auto-packing in outbound delivery via IDOC process.
Can anybody through some light on the above requirement in finding Message type, process code and so on...
your every suggestion or hint will help me to fulfill the requirement.
Thanks in advance.
Best Regards
Suresh.

Hi,
Auto Packing message type: SDPACK
Process code: SDPA
Basic type: SDPAID01
Regards
Suresh.

Using MBGMC Message Type To Post Auto Goods Receipt in ECC

We are using Basic Idoc Type :MBGMCR02 to Post Auto Goods Receipt in ECC.
This happens when external system ( 3rd Party System) sends this message which in turn posts the GR in ECC.
Thru Goods Movement BAPI
My Question is CAN WE POST auto goods receipt thru MBGMCR02 with Inbound delivery as reference document - Instead use ASN ( Advanced shipping notification ) which is Reference document in inbound delivery to Post Goods receipt in ECC.
This is required for our integration peice with 3rd party system.
And also pl let me if we can use Basic types MBGMCR01 or MBGMCR03 to post auto goods receipt in ECC with reference to PO which has confirmation control key set and instead of passing inbound delivery number can we pass ASN number which is external delivery ( Reference ) number and post goods receipt successfully in ECC.
Would appreciate your immediate help in this regard.
Regards,
Mahesh

We have used Message type : WMMBXY with an enhancement to user exit to mark status of inbound delivery to complete after entire quantity of Inbound delivery has been received.
Thanks,
Mahesh

Question about auto packing

Hello,
as i saw the post about auto packing in delivery
the config steps are described as follow
1) Create the packing Material In MM01 of material Type 'VERP'
2) Create packing Instructions from TA: POP1
3) packing Determination in POF1 ... for MM Condition type is RCPT and for SD its is SHIP. So create condition records here.
4) In Customization SPRO-> Logistic Execution-> Shipping-> Deliveries->Define Delivery Types
In Delivery, there is Check box for automatic packing.
First , i tried to create condition value in POF1 for SHIP as condition type and put my Packing instruction e.g. 233 into it.
but it wont work in my delivery e.g. LF.
secondly I tried to create in POF1 for ZVPA, with my Packing Instruction 233, and then it works in my delivery.
So my question is, the condition type for HU/ Auto Packing, how are they connected to my documents/ processes e.g. I use OR as sales order, and LF as delivery.
in the Picture below, i can see both condition type SHIP and ZVPA are using SHIP as acc.sequence. So which condition would be used when I create my delivery ? and how to configure that?
Thanks!

Hi,
this defined in custo:
Click on maintain packing transaction profile and the select for instance 0002 Outbound delivery
Here is defined what procedure determination will be used in entry field Determ. proc. for pkg intrs
Then you define for this procedure what conditions will be available
Select the procedure determination you defined in previous step and you maintain the conditions
If reply answer your question close discussion <Text removed by Moderator for point begging. In addition to that discussion is unmarked as question, as this is encouraging point gaming and lobbying for points. Even both OP & "Star" contributor ignored Moderator comments. You both are advised to review SCN RoE and adhere them in your future conduct.>
Regards,
JM
Message was edited by Moderator: Jyoti Prakash

What is inbound XML message type and idoc type in Purchase Order response

Hi ,
We are on SRM 7 ECS , support pack SAPKIBKV08.
We have a process in which vendor will send a Purchase Order response which will be
converted to XML format by a middleware. This XML message will come to
SRM and post a POR. I want to do the EDI mapping for this XML message,
but there is no message type and idoc type in SRM for Purchase Order
response. How do I map my message type in SRM to the vendor sent fields
in middleware .
Please advise
Rgds
Sumendra

Hi,
You can process with XML without IDoc.
Vendor-> (XML) -> PI -> (XML) -> SRM.
Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
http://esworkplace.sap.com
Regards,
Masa

Assign an output type to a message type

Hi all,
How do I assign an output type to a message type?
Thanks in advance.
JM

You maintain the output type determination settings for the inbound and outbound delivery handlers, so that output types can be determined for deliveries, pursuant to the message control mechanism.
<b> a. You maintain the output types in Customizing for Logistics - General ->upply Chain Planning Interfaces (SCPI)-> Auto-ID Backend Integration->IDoc Processing ->Operational IDocs -> Output Type Determination -> Output Type Determination for Inbound/Outbound Deliveries-> Maintain Output Types</b>.
reward points if it is usefull....
Girish
<b></b>

Output message type not triggered for few POs

---PRs got created manually. then PRs converted into POs through background job (me59n).
( 25 PRs got created manually with same vendor and pur.org combination then all PRs converted into POs through ME59N. In that 20 PRs had message type automatically but remaining POs haven't got the message type )
Condition record exists with vendor/pur.org combination.
and all IMG settings are correct.
medium is 8 (special function).
and not able to replicate the issue in quality systems.
Please Advise.
Thanks in advance.

PRs will not get any message type, POs will get a message record.
How is the situation now?
Did you get 20 POs only, or do you have 25 POs where just 20 have a message record?
In the first case convert the PR manually to a PO manually and see if you get a message record. You should not enter anything manually, it is supposed to work without entering anything manually because it was meant for auto PO. In case you have to enter anything manually, then this might be an indicator why auto PO could not work.
if the latter case, then compare a PO with and without message record on the fields that should match with your condition record.
Do you expect the same message type for all POs, are they all in the same purchasing organisation?
Read and check what is mentioned in KBA 1829682 - Output type is not determined in Purchase order

Message type SHPCON, idoc type DELVRY01

Hi SAP Gurus,
I am using message type SHPCON and idoc type DELVRY01 with processing code DELV to post goods issue for a delivery note.
I tried to simulate the inbound entry via WE19. I was not able to proceed with the posting because I encountered error 51 in idoc.
Field EXIDV empty
Field VHILM empty
These fields are in E1EDL37 and E1EDL44 respectively, and referring to HU information in which we don't have.
What I have filled up are the fields:
E1EDL20-VBELN = DO num
E1EDL20-VSTEL = Plant
E1EDL18-QUALF = "PGI"
E1ADRM1-PARTNER_Q = "WE"
E1ADRM1-PARTNER_IQ = recv plant
E1EDTH13-QUALF = "015"
E1EDTH13-NTANF = date today
E1EDL24-POSNR = 000010
E1EDL24-MATNR = material num
E1EDL24-WERKS = delv plant
E1EDL24-LGORT = sloc
E1EDL24-LFIMG = quantity
E1EDL24-VRKME = unit
E1EDL24-LGMNG = quantity
E1EDL24-MEINS = unit
May I know how to avoid this or if I missed some fields that resulted to this error ? Or am I using the wrong message type?

Hari,
I can definitely use WE19 to reprocess it. However my problem is the source of this information. If we implement this process, we would not know where to get this information since we don't use handling units. To add to this, the field VHILM that the system is asking is "packaging material" which we don't use and don;t have.
How to get rid of these fields? In VL02N, there is no handling units when I click on the pack icon. Only the material and the quantity.
Thanks.

Idoc type, message type and process code for EDI 940 & 945

Hi,
We are implementing a scenario wherein we are required to send a Wharehouse Shipping Order to the warehouse (forwarding agent) using EDI 940. The output of the o/b is triggered from the Delivery (VA01) after creation of a Delivery in SAP. Once the warehouse ships the goods, it notifies us back by sending EDI 945 (Warehouse Shipping Advice). Using this inbound 945 we are required to update the existing delivery in SAP, i.e., it should do the Pick, Pack and PGI.
Can someone tell me which Idoc type, Message Type and Process code should be used for the above scenario.
Thanks in advance for the help.
Regards,
Gajendra

Hi Gajendra,
For EDI940, you can use message type SHPORD or WHSORD, IDOC type DELVRY01 and process code DELV.
For EDI945, you can use message type SHPCON or WHSCON, IDoc type DELVRY01 and process code DELV.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Shipment IDOC basic type TPSSHT01 Message type SHIPPL

Hi,
I tried changing the shipment to add a delivery to the shipment using a bapi. I have successfully added the delivery but INbound IDOC but finally i ended up in error in the idoc stating "Transportation planning point has no partner for transportatn. planning"
please let me know where am goin wrong.
Thanks,
Prem.

Hi Sravan ,
WE82 is used for - Assigning Message type to IDOC . Here only we assigned this WMTORD message type to IDOC (DELVRY03).
We have warehouse , we need to send the WMTORD ( Transport order ) to Warehouse . Then they can process the picking , packing , shipping and loading and send the materials to customers . After completion of all process , they(WMS team) will send the WMTOCO ( Transport confirmation ) to us .Then We will generate the Invoice based on TO and purchase Order .
My requirement : Now , The warehouse team needs the delivery date also should include in WMTORD message .
But i looked in all segments in DELVRY03 idoc , i didn't find any element belongs the delivery date .
Please advice me and help on this same

Add Namespce and message type to incoming file

Hi Experts,
I have a file to Idoc scenario where my input file comes without a name space message type like this
<?xml version="1.0" encoding="UTF-8"?>
<Header>
    <Field>
      <FieldSeparator/>
      <EncodingCharacters/>
      <SendingApplication/>
</Field>
     In PI I have created the data type in a particular namespace and the message type, so when this file is polled for at the source folder, it fails in the moni
any idea on how to proceed ??
Regards,
Teja

Hi Ravi,
You can do it with a simple JAVA mapping.
You need to add this Java Mapping in Operation mapping Before your actual graphical mapping.
INPUT:
<?xml version="1.0" encoding="UTF-8"?>
<Header>
<Field>
<FieldSeparator/>
<EncodingCharacters/>
<SendingApplication/>
</Field>
</Header>
OUTPUT:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MessageType xmlns:ns0="urn:sap.com:test:mapping:java">
<Header>
<Field>
<FieldSeparator/>
<EncodingCharacters/>
<SendingApplication/>
</Field>
</Header>
</ns0:MessageType>
Please find the Java code.
package addMessageTypeAndNamespace;
import java.io.BufferedInputStream;
import java.io.ByteArrayOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.OutputStream;
//1. AbstractTransformation class is imported.
import com.sap.aii.mapping.api.AbstractTransformation;
import com.sap.aii.mapping.api.InputAttachments;
import com.sap.aii.mapping.api.InputParameters;
import com.sap.aii.mapping.api.InputPayload;
import com.sap.aii.mapping.api.OutputAttachments;
import com.sap.aii.mapping.api.OutputHeader;
import com.sap.aii.mapping.api.OutputParameters;
import com.sap.aii.mapping.api.OutputPayload;
import com.sap.aii.mapping.api.StreamTransformationException;
import com.sap.aii.mapping.api.TransformationInput;
import com.sap.aii.mapping.api.TransformationOutput;
import com.sap.aii.mapping.api.InputHeader;
public class addMessageTypeAndNamespace extends AbstractTransformation{
     public void transform(TransformationInput arg0, TransformationOutput arg1) throws StreamTransformationException
          try {
               String strinput=readInputStreamAsString(arg0.getInputPayload().getInputStream());
               String withoutXmlDeclaration=strinput.substring(39, strinput.length());
               String XmlDeclaration=strinput.substring(0, 38);
               strinput=XmlDeclaration+"<ns0:MessageType xmlns:ns0=\"urn:sap.com:test:mapping:java\">"+withoutXmlDeclaration+"</ns0:MessageType>";
               arg1.getOutputPayload().getOutputStream().write(strinput.getBytes("UTF-8"));
          } catch (IOException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
          catch (NullPointerException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
               getTrace().addInfo(e.getMessage());
public static String readInputStreamAsString(InputStream in)      throws IOException
     BufferedInputStream bis = new BufferedInputStream(in);
     ByteArrayOutputStream buf = new ByteArrayOutputStream();
     int result = bis.read();
     while(result != -1)
          byte b = (byte)result;
          buf.write(b);
          result = bis.read();
     return buf.toString();

Simultaneous auto packing of multiple deliveries using trans. VL02N

Standard SAP does not allow simultaneous auto packing of multiple deliveries contained in one shipment in transaction VL02N. so i need to create custom transaction to allow the user to auto pack one or more deliveries simultaneously.I tried using recording of transaction VL02N for group of deleviries and it shows error in status message. is there any possiblity i can do auto pack of group of deleviries.

resolved

Finding Process Code for a message Type

Hi,
Is there any way to find process code for a specific message type.
Message Type WFRESOURCE_CHANGEAVAILABILITY

Hi Swathi,
I have already mention the process codes that can be used for this message type. For your convenience i am also attaching th description ,which process code can be used when.
ABI_AIDN_IN     Auto- ID Idoc process
ED00                Display Idoc using work item
ED00_XML        Display idoc using work item (xml)
ED08                Forward idoc
ZABI_DLV_IN    Delivery advice ( AIDDESADV with DELVRY04)
Regards
Vinod

Output message type determination through MIGO

hello experts,
I am doing MIGO for goods reciept, it is creating material document and triggering output type attached to it (ZLCO).
Same thing when i am doing through an excel sheet (this excel application is calling a Z function module thats one looks is calling Standard BAPI BAPI_GOODSMVT_CREATE), this is creating material document but not trigger output type.
Output ZLCO is not created upon VGR thru Excel Upload.
What part of code should i provide to my Z function module so that it also trigger the Output type.
Thanks,
Sumit

PRs will not get any message type, POs will get a message record.
How is the situation now?
Did you get 20 POs only, or do you have 25 POs where just 20 have a message record?
In the first case convert the PR manually to a PO manually and see if you get a message record. You should not enter anything manually, it is supposed to work without entering anything manually because it was meant for auto PO. In case you have to enter anything manually, then this might be an indicator why auto PO could not work.
if the latter case, then compare a PO with and without message record on the fields that should match with your condition record.
Do you expect the same message type for all POs, are they all in the same purchasing organisation?
Read and check what is mentioned in KBA 1829682 - Output type is not determined in Purchase order

RFC dump : 'Message type " " is unknown.'

Hi everyone,
I am calling an RFC from one system to another and i am getting a dump with error :
Message type " " is unknown.
When i debugged the program the found that nothing is returned for " MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. "
What should i do to rectify the problems? Please do help.
Thanks In Advance.
Regards,
Heera

ABAP runtime errors    MESSAGE_TYPE_UNKNOWN
       Occurred on     03/05/2008 at 21:56:28
Message type " " is unknown.
What happened?
The current ABAP/4 program "Y_MM_C_CICS_MAT_RECON " h
because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 progra
What can you do?
Print out the error message (using the "Print" functi
and make a note of the actions and input that caused
error.
To resolve the problem, contact your
SAP system administrator.
You can print this message by choosing "Print".
Transaction ST22 allows you to display and manage sho
is especially useful if you want to keep a particular
Error analysis
Only message types A, E, I, W, S and X are allowed.
How to correct the error
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"MESSAGE_TYPE_UNKNOWN"
"Y_MM_C_CICS_MAT_RECON " bzw. "Y_MM_C_CICS_MAT_RECON "
"START-OF-SELECTION"
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.............. "46B"
Application server....... "fmsap591"
Network address.......... "10.19.196.114"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x IA64 Level 3"
Database server.......... "FMSAP591"
Database type............ "ORACLE"
Database name............ "AI0"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "46D"
Created on............... "Jul 30 2007 00:11:29"
Created in............... "NT 5.0 2195 Service Pack 2 x8
Database version......... "OCI_920_SHARE__OCI_7_API "
Patch level.............. "2335"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.0.5.., ORACLE 8.0.
8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 1
SAP database version..... "46D"
Operating system......... "Windows NT 4.0, Windows NT 5.
Windows NT 5.2, , System build information:,
                                      , LCHN : 921411"
User, transaction...
Client.............. 250
User................ "HPRAMANX"
Language key........ "E"
Transaction......... "SE38 "
Program............. "Y_MM_C_CICS_MAT_RECON "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP/4 program "Y_MM_C_CICS_MAT_RECON " in
"START-OF-SELECTION".
The main program was "Y_MM_C_CICS_MAT_RECON ".
The termination occurred in line 371
of the source code of program "Y_MM_C_CICS_MAT_RECON " (when calling the editor
3710).
Source code extract
003410       r_lgort-sign = 'I'.
003420       r_lgort-option = 'EQ'.
003430       r_lgort-low = x_storeloc_wa-ecc_st_locn.
003440       APPEND r_lgort.
003450     ENDLOOP.
003460
003470
003480   *CALL RFC TO GET MATERIAL DATA FROM F PIPE BY PASSING S_MATNR r_werks
003490   *r_lgort S_CHARG AND GETTING THE REQUIRED DATA BACK IN THE TABLE
003500   *I_MCHBF
003510
003520     CALL FUNCTION 'YCICS_MATERIALDATA'
003530     DESTINATION 'FI0250'
003540          TABLES
003550               i_matnr                        = s_matnr
003560               i_werks                        = r_werks
003570               i_lgort                        = r_lgort
003580               i_charg                        = s_charg
003590               i_mchb                         = i_mchbf
003600          EXCEPTIONS
003610               no_data_found                  = 1
003620               material_not_of_type_fert      = 2
003630               invalid_plant_entry            = 3
003640               invalid_stloc_entry            = 4
003650               invalid_plnt_matnr_combi       = 5
003660               invalid_plnt_matnr_batch_combi = 6
003670               invalid_plnt_matnr_batch_stloc = 7
003680               OTHERS                         = 8.
003690     IF sy-subrc <> 0.
003700    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
     >            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
003720     ENDIF.
003730
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 1                             SY-INDEX 0
SY-TABIX 1                             SY-DBCNT 31
SY-FDPOS 0                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+....4
VARI
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40                                          ####00000000000000
                               2222222222222222222200003333333333333322
                               0000000000000000000000000000000000000000
... + 80                          ####################################
                               2222000000000000000000000000000000000000
                               0000000000000000000000000000000000000000
... + 120                      ########################################
                               00000000
                               0000000
SY-MSGV1
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
SY-MSGV2
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                              0000000000
Y-MSGV3
                              2222222222222222222222222222222222222222
                              0000000000000000000000000000000000000000
.. + 40
                              2222222222
                              0000000000
Y-MSGV4
                              2222222222222222222222222222222222222222
                              0000000000000000000000000000000000000000
.. + 40
                              2222222222
                              0000000000
_MCHB                         #######################################
                              0000000000000000000000000000900000009000
                              0000000000000000000000004000060000001000
.. + 40                      ####0###0#######ÿÿÿÿ:###########è ####
                              1000300030000000FFFF300000000000EA280000
                              0000020001000000FFFFA000200043008D030000
.. + 80                      x> ####################################
                              7328000000000000000000000000000000000000
                              8E03000000000000000000000000000000000000
.. + 120                      ########################(#######
                              00000000
                              0000000
MCHBWA                      000000000000895405CR01CRA10001    CR01TE
                              3333333333333333334533454333332222453354
                              0000000000008954053201321100010000320145
.. + 40                      ST05####e#########
                              553300006000000000
                              3405000150C000000C
SCHARG_%_APP_%              S_CHARG S_CHARG                       to
                              5544454255444542222222222222222222222276
                              3F3812703F38127000000000000000000000004F
.. + 40
                              2222222222222222222222222222222222222222
                              0000000000000000000000000000000000000000
.. + 80                         @1FQMultiple selection@
                              2224345547676766276666766642222222222222
                              000016C1D5C490C5035C5349FE00000000000000
.. + 120
                               222
                               000
X_MCHBF_WA
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40                      00000000            00000000
                               3333333322222222222233333333222222222222
                               0000000000000000000000000000000000000000
... + 80                      000000 #################################
                               3333332000000000000000000000000000000000
                               0000000000000C000000C000000C000000C00000
... + 120                      ########################################
                               00000000
                               0C00000
I_MCHBF                        ################@#######################
                               0000000000000000400000000000100000000000
                               1000400040004000080050004000080000000000
... + 40                      ################ÿÿÿÿÓ###################
                               1000000000000000FFFFD0000000000000000000
                               0000000000000000FFFF30007000630000000000
... + 80                      ########################################
                               0000000000000000000000000000000000000000
                               0000000000000000000000000000000000000000
... + 120                      ########################8#######
                               00000000
                               0000000
SYST                           ########################################
                               0000000000000000000000000000000000000000
                               0000000010000000000000000000000000000000
... + 40                      ####################ã###################
                               10000000000000000000E0000000000000000000
                               F00000001000000010003000000000000000F000
... + 80                      ########################################
                               0000000000000000000000000000000000000000
                               0000000000001000800000000000000000000000
... + 120                      #######################################
                               00000000
                               0000000
X_MKPFMSEG_WA-BKTXT
                               2222222222222222222222222
                               0000000000000000000000000
%_SPACE
                               0
                               0
X_OUTPUT_WA-BTEXT
                               22222222222222222222
                               00000000000000000000
X_MCHB_WA-MATNR                000000000000895405
                               333333333333333333
                               000000000000895405
X_MKPFMSEG_WA-WERKS
                               2222
                               0000
X_MCHB_WA-WERKSF               CRA1
                               4543
                               3211
X_OUTPUT_WA-WERKS
                               2222
                               0000
X_MCHB_WA-LGORTF
                               2222
                               0000
X_MKPFMSEG_WA-LGORT
                               2222
                               0000
X_MCHB_WA-CHARG                CR01TEST05
                               4533545533
                               3201453405
Active calls / events
No.... Type........ Name..........................
       Programm
       Include                                  Line
     1 EVENT        START-OF-SELECTION
       Y_MM_C_CICS_MAT_RECON
       Y_MM_C_CICS_MAT_RECON                      371
Internal notes
The termination occurred in the function "ab_jmess" of the SAP
Basis System, specifically in line 1083 of the module
"//bas/46D/src/krn/runt/abdynpro.c#22".
The internal operation just processed is "MESS".
The internal session was started at 20080305215621.
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App       : disp+work.EXE (pid=24072)
When      : 3/5/2008 21:56:28.0
Threads   : 2
Computer Name       : FMSAP591
User Name           : ai0adm
Number of Processors: 2
Processor Type: ia64 Family 31 Model 1 Stepping 5
Windows Version     : 5.2 Current Build: 3790
Stack Dump for Thread Id 56f4
FramePtr         ReturnAd         Param#1          Function Name
00000000083a0c00 0000000076eab530 00000000000024f4 kernel32!GetDateFormatW
00000000083a0bd8 000000000215a7c0 00000000000024f4 kernel32!GetDateFormatW
00000000083a0b88 000000000067fe80 0000000000000080 disp+work!
000000001c1b0040 0000000076ea7420 0000000000212e50 MSVCRT!tanhf
000000001c1b0000 0000000000000000 000006fb7eb36e88 kernel32!GetDateFormatW

Auto Packing Message Type

Similar Messages

Maybe you are looking for