MESSAGE_TYPE_X ABAP Dump

[Former Member]

Hi,

I am getting this error when we are trying to run the batch jobs. the message class is CO . Can anybody please suggest as how can i look into this issue.

The following is the analysis from the Dump

Error analysis

Short text of error message:

Forward scheduling (enter start date)

Long text of error message:

Technical information about the message

Message classe...... "CO"

Number.............. 027

Variable 1.......... 6017907

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

thank u,

Irshad Mohammed

[Former Member]

Please assign tick the current date as forwarding date for plant setting in Tcode OIO8.

Regards,

Sachin

[Former Member]

Hello ,

I have the same problem also a short dump .

Happened by entering forecast days .

Can anybody give me the right Sap Note where i can see what to do ?

Thank You

Davy

[markus_doehr2]

Too less information.

What program is dumping? Did you search for the program name for sap notes? What release + support package level are you running?

--

Markus

[Former Member]

I am running a custom program. I am using 4.6C, SP level 50. OS AIX 5.3, DB DB2. I searched marketplace but was unable to find the sol.

[markus_doehr2]

I´m sorry - if you won´t (or can´t) give more information about the dump it´s impossible to help you.

That dump is a generic exception and without a full context, nobody will be able to help you.

--

Markus

[Former Member]

BAP runtime errors MESSAGE_TYPE_X

Occurred on 11/26/2007 at 00:37:26

-

-

---

>> Short dump has not been completely stored. It is too big.

-

-

---

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 the actions and input that caused the error.

Inform your SAP system administrator.

You can print out this message by choosing "Print". Transaction ST22

allows you to display and manage termination messages, including keeping

them beyond their normal deletion date.

-

-

---

Error analysis

-

-

---

Short text of error message:

Forward scheduling (enter start date)

Long text of error message:

Technical information about the message:

Message classe...... "CO"

Number.............. 027

Variable 1.......... 6017907

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

-

-

---

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_X"

"SAPLCOZF " or "LCOZFU13 "

"CO_ZF_ORDER_SCHEDULE"

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.............. "46C"

Application server....... "locke"

Network address.......... "192.168.64.139"

Operating system......... "AIX"

Release.................. "5.3"

Hardware type............ "00C7F2DE4C00"

Database server.......... "newton"

Database type............ "DB6"

Database name............ "PRD"

Database owner........... "SAPR3"

Character set............ "en_US.ISO8859-1"

SAP kernel............... "46D"

Created on............... "Feb 20 2007 20:27:40"

Created in............... "AIX 1 5 00447C4A4C00"

Database version......... "DB6_71 "

Patch level.............. "2307"

Patch text............... " "

Supported environment....

Database................. "DB6 06., DB6 07., DB6 08., DB6 09."

SAP database version..... "46D"

Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3

5, , System build information:, -

-

---

, LCHN :

891347"

-

-

---

User, transaction...

-

-

---

Client.............. 100

User................ "BATCHPS"

Language............ "E"

Transaction......... " "

Program. ........... "SAPLCOZF "

Screen. ............ "SAPMSSY1 3004"

Line of screen...... 2

Information about Remote Function Call (RFC) Caller:

System.............. "PRD "

Database release.... "46C "

Kernel release. .... "46D "

Connection type. ... "3 " (2 = R/2, 3 = R/3, E = Extern, R = Reg.

Call type........... "A-" (S = synch., a/A = asynch., T = transactional

Client.............. 100

User................ "BATCHPS "

Transaction......... " "

Function module..... "HB_ORDER_CHANGE_FOR_ACTIVITY_W"

Call destination.... "locke_PRD_30"

Source server....... "locke_PRD_30"

Source IP address... "192.168.64.139"

Additional information about RFC logon:

Trusted relationship " "

Logon return code... 0

Trusted return code. 0

Note: In Releases earlier than 4.0, some of the above information about

RFC calls may not be available.

-

-

---

Information on where termination occurred

-

-

---

The termination occurred in the ABAP/4 program "SAPLCOZF " in

"CO_ZF_ORDER_SCHEDULE".

The main program was "SAPMSSY1 ".

The termination occurred in line 408

of the source code of program "LCOZFU13 " (when calling the editor 4080).

-

-

---

Source code extract

-

-

---

003780 CAUFVD_EXP-GSTRP = CAUFVD_EXP-GLTRS.

003790 ELSE.

003800 CAUFVD_EXP-GLTRS = CAUFVD_EXP-GSTRP.

003810 CAUFVD_EXP-GSTRS = CAUFVD_EXP-GSTRP.

003820 ENDIF.

003830 ELSE.

003840 CAUFVD_EXP-GLTRS = CAUFVD_EXP-GLTRP.

003850 CAUFVD_EXP-GSTRS = CAUFVD_EXP-GSTRP.

003860 ENDIF.

003870 * Freigabetermin löschen

003880 CLEAR CAUFVD_EXP-FTRMS.

003890 * Terminierung erfolgt

003900 CAUFVD_EXP-FLG_TRME = 'X'.

003910 PERFORM CAUFV_UPD(SAPLCOBH) USING CAUFVD_EXP.

003920 * Status 'Termine nicht aktuell' zurücksetzen

003930 PERFORM RESET_STATUS_NTER(SAPLCOBH) USING CAUFVD_EXP.

003940 * Termine in die Position schreiben

003950 PERFORM POSITION_UPDATE USING CAUFVD_EXP CAUFVD NO_QUOTA.

003960

003970 ELSEIF SY-SUBRC = 3.

003980 * Kein Starttermin angegeben, Terminierung abgebrochen

003990 CALL FUNCTION 'T482_READ'

004000 EXPORTING

004010 I_TERMKZ = CAUFVD_EXP-TERKZ

004020 IMPORTING

004030 T482_EXP = T482.

004040

004050 IF NOT T482-NTERM IS INITIAL.

004060 MESSAGE X029(CO) WITH CAUFVD_EXP-AUFNR.

004070 ELSEIF NOT T482-VORWT IS INITIAL.

-

-

---

MESSAGE X027(CO) WITH CAUFVD_EXP-AUFNR.

004090 ENDIF.

004100

004110 ELSEIF SY-SUBRC = 4.

004120 * Kein Endtermin angegeben, Terminierung abgebrochen

004130 CALL FUNCTION 'T482_READ'

004140 EXPORTING

004150 I_TERMKZ = CAUFVD_EXP-TERKZ

004160 IMPORTING

004170 T482_EXP = T482.

004180

004190 IF NOT T482-NTERM IS INITIAL.

004200 MESSAGE X029(CO) WITH CAUFVD_EXP-AUFNR.

004210 ELSEIF NOT T482-RUEKT IS INITIAL.

004220 MESSAGE X028(CO) WITH CAUFVD_EXP-AUFNR.

004230 ENDIF.

004240

004250 ELSEIF SY-SUBRC = 5.

004260 * Keine Terminierungsparameter, Terminierung abgebrochen

004270 IF MSGNO IS INITIAL.

-

-

---

Contents of system fields

-

-

---

SY field contents..................... SY field contents.....................

-

-

---

-

-

---

-

-

---

-

-

---

SY-SUBRC 0 SY-INDEX 1

SY-TABIX 278 SY-DBCNT 0

SY-FDPOS 266 SY-LSIND 0

SY-PAGNO 0 SY-LINNO 1

SY-COLNO 1

[markus_doehr2]

Does maybe

Note 410405 - Termination MESSAGE_TYPE_X after implementatn of Note 408612

apply?

--

Markus