Notification IDOC Type INOTIF01 failing in poasting
Hi,
I have a program which extract data and post IDOC for notification of Type INOTIF01. The program was working fine in SAP 4.6C. As in ECC6.0, SAP has introduced an addition popup in IW32 transaction, thus my IDOC generation and posting program is failing while posting IDOC as it is not able to handle that new popup.
IT is using function module "IDOC_INBOUND_ASYNCHRONOUS" to process the IDOC data populated in Control and Data Tables.
Pls advice what i can do to handle this new popup which is causing problem and IDOC is failing.
thanks and all help is appreciated.
Sandy
Hi,
It is a custom program which is using IDOC Type INOTIF01 and Message TYpe INOTIF. It populate Data in IDOC CONTROL & IDOC Data internal tables.
After Populating data in internal tables, it uses "IDOC_INBOUND_ASYNCHRONOUS" function module to create and post IDOC.
I checked in EDIMSG table and for message Type INOTIF , IDOC Type INOTIF01 is linked and it has entries upto 46C version only. there is no entry in table for 700 version for message Type INOTIF.
Similar Messages
-
Idoc segment for shpmnt notification for idoc type shpmnt02
Hi gurus,
I have to find the idoc segment for shipment notification,idoc type which we are going to use is shpmnt02 or shpmnt01,Can any one of you please tell me the idoc segments for this idoc type with fields and table name?.Thanks in advance.Hi Nagarathinam
You can use transaction WE60 for documentation on IDOCs
Best regards,
Chris -
Idoc type for pm notifications
hi all,
can anyone give me names of the Idoc type for triggering pm notification.
with regards,
SyedOk, I found it.
FL: MDM_FUNCLOC_SAVEREPLICA
EQ: MDM_EQUIPMENT_SAVEREPLICA
Thanks! -
Error while creating an outbound idoc using idoc type delvry02
hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leoThe message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful. -
IDoc type could not be determined for the IDoc in F110
Dear All,
The below mentioned error is encountered by us in F110.We have check all the setiing and not able to find the solution for this error.
Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
The system is not creating the IDOC file.....
IDoc type could not be determined for the IDoc
Message no. B1090
Diagnosis
The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type from field DOCTYP.
Procedure
Possible error sources:
- The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
- The IDoc type is not known in your system and must be maintained.
Kindly do the needful.
RegardsIf you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition. -
Get Idoc Types Processed by Jobs Running Programs RBDAPP01 or RBDMANI2
Hi Everyone! I would just like to ask if there is a way I can identify all background jobs which are processing a specific idoc type in SAP?
For example, I want to get the Jobs that are processing inbound idoc type WMMBXY using program RBDAPP01 or RBDMANI2.
Is there a way to extract this information?
Thanks in advance!Vincent, we have a conservative approach RE those programs that re-process IDOCs in pending or error status : we do not define those jobs with open selections, instead we are specific in terms of message type and partner where applicable. We also set a limit in the number or attempts on a failed IDOC by setting a 'rolling start date' (like current date - 7). Besides audit considerations about lingering processes, you also need to take into account the impact of this process on the tale size. Each time the job runs and the IDOC fails, a status record will be added to the EDIDS table for each of those IDOC. If you do not pay attention, you may end up with large amounts of data. This is not only going to unplease your BASIS and DB administrator but eventually put in jeopardy your archiving process (wchich could lead to a system crash !!).
We usually aslo complement those jobs with a status change step (moving from error to no further processing) ; the date parameter can be set to something like anythiing with a creation date > current date + 3 months
To come back to your question : SM37 using the program name as parameter will help you find the associated jobs, but you might need to look into the step(s) and associated variant to get the messages those jobs / steps are processing -
IDOC Types and their equivalent messages in EDIFACT and ANSI X12
Hi all, since I only have a list of messages in EDIFACT and ANSI X12 for release 4.6 B, I need to update the list from 6.0 version, but I don't have online support system to get it (OSS), it's note 104606 in OSS.
Can somebody give me a link to the full new updated list? Will surely give points with your helpful answers
Regards,Hi,
Please check these perhaps they may help.
Mapping ANSI X12 to SAP Message Type and IDoc Type:
204 Motor carrier shipment information
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880), EDI - Inbound INVOIC posting configuration
The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
The logical message is DELINS (from the EDI standard ODETTE) or DELFOR, the IDoc type is DELFOR01.
832 Price catalog (also 879, 888, 889)
The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04. Outbound processing is supported.
850 Purchase order or order (also 875)
The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
The logical message is PROACT, the IDoc type PROACT01.
855 Ordering or order response (also 865)
The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
For delivery in the SAP application, the logical message is DESADV, the IDoc types are DESADV01 (expires) or DELVRY01 and DELVRY02.
860 Ordering or order modification (also 876)
The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
The logical message is GSVERF, the IDoc type GSVERF01.
862 delivery schedule (FAB)
The logical message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDoc type is DELFOR01.
864 Text message
The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional Acknowledgment
This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
"22" Shipping OK, acknowledgment has yet to come
"16" Functional Acknowledgment positive
"17" Functional Acknowledgment negative
The status values "14" and "15" are available for the Interchange Acknowledgment accordingly.
Regards,
Ferry Lianto -
hi,
i need the list of message types and idoc types for edi.
can any one of u pls send it.Hi,
Check the OSS notes 104606.
The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
204 Motor carrier shipment information
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880)
The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
832 Price catalog (also 879, 888, 889)
The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
850 Purchase order or order (also 875)
The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
The logical message is PROACT, the IDoc type PROACT01.
855 Order confirmation (also 865)
The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
860 Ordering modification (also 876)
The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
The logical message is GSVERF, the IDoc type GSVERF01.
862 Delivery schedule (FAB)
The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
864 Text message
The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional acknowledgment
This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
"22" Shipping OK, acknowledgment has yet to come
"16" Functional acknowledgment positive
"17" Functional acknowledgment negative
The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
Cheers
VJ -
IDOC Type - TRXSTA01 is missing in 4.6 C
Hi ,
Though TRXSTA01 is supported by SAP . We are not able to find the same in 4.6 C
The following 'basic IDOC type' is not available .
IDOC Type: TRXSTA01
Message Type: TRXSTA
Process code: TRXS
Function Module: BORTE_IDOC_INPUT_TRXSTA.
The IDOC type is basically used for shipment status notification.
It seemes to be release issues .
Any help will be appriciated .
Regards
SamirHi Sameer,
Welcome to SDN.
Perhaps you can use this IDoc type and message type instead.
- DELVRY03/DESADV for shipping notification.
- SHPMNT05/SHPADV for shipment message.
For more information, please check this link.
http://help.sap.com/saphelp_erp2005/helpdata/en/25/42a5ca89bf11d288de0000e8214d78/frameset.htm
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful. -
IDoc type "DELVRY03" for INBOUND delivery confirmation and Outbound Deliver
Hi ,
We have a requirement where we have to send Inbound delivery confirmation as well as outbound delivery notification to our same customer. (3PL case)
We have a EDI partner who is receiving our messages and transforming them before sending it to customer.
Now my problem is , since I am using same idoc type (DELVRY03) for both cases therefore wondering how my EDI partner will differentiate whether received message is a INBOUND delivery confirmation or OUTBound delivery notification.
regards
ShreyThx for your reply ...
Wondering about the impacts , if I create a new message type like ZDESADV and attach it to DELVRY03.
In this i could have two message types DESADV and ZDESADV.
Will it impact anywhere ?
Regards
Shrey -
Multiple customers in Sender Party for IDOC type KU
Hi All,
My scenario is IDOC to HTTP with sender IDOC Type KU.
We are using PO 7.4 and IDOC_AAE.
I have done the following settings.
Created a Sender Party and assigned a customer under party identifiers. (Also I can't add multiple values with same Agency and scheme it throws eror in PI)
For a single customer the end to end scenario is working fine.
But if I try to send the IDOC with other customer Number it fails as the entry is not maintained for that customer in Sender Party identifiers.
Also I can't afford to create a different party for each customer as there are hundreds of customers in the ECC Application system.
I also tried with value mapping but it won't worked.
Please suggest on this.
Regards,
Nitin...Dear Nitin,
did you solve this problem? A am faced to it right now... ...
Regards,
Markus -
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,
GajendraHi 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. -
Message type idoc type problems
Hi,
I'm facing a problem in idocs. I'm sending idocs with message type ORDRSP and idoc type ORDERS05, but for some reason in SAP, the idoc is always picking up a different message type ORDERS and the partner profile part is failing because my partner profile is set up for ORDRSP message type. Is there any setting or transaction that sets a default message type for an idoc type in SAP.
Regards,
VijayHi vihay,
yes for the message type ordrsp the basic type is orders05.
u r telling ur geeting problem in inbound idoc?
if that is the case then u have to use in we20 inbound parameters and give the processcode(ORDE) there instead of basictype .CHECK the same and get back to me if any quries
Regards,
Nagaraj -
ORA-27369: job of type EXECUTABLE failed with exit code
am getting this error
ORA-27369: job of type EXECUTABLE failed with exit code: Operation not permitted.
We have been using this for such a long time without any problems.this is the plsql scheduler :
Please help
BEGIN
SYS.DBMS_SCHEDULER.CREATE_JOB
job_name => 'PROD_LOAD_SL_FILES'
,start_date => TO_TIMESTAMP_TZ('2005/12/02 17:05:00.000000 -05:00','yyyy/mm/dd hh24:mi:ss.ff tzh:tzm')
,repeat_interval => NULL
,end_date => NULL
,job_class => 'DEFAULT_JOB_CLASS'
,job_type => 'EXECUTABLE'
,job_action => '/home/oracle/actual/payment_files/slc_prod/load_sl_files.sh'
,comments => 'Loads SL files, uploads logs to database and sends email to Disbursement and DBA teams'
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'PROD_LOAD_SL_FILES'
,attribute => 'RESTARTABLE'
,value => FALSE);
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'PROD_LOAD_SL_FILES'
,attribute => 'LOGGING_LEVEL'
,value => SYS.DBMS_SCHEDULER.LOGGING_RUNS);
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
( name => 'PROD_LOAD_SL_FILES'
,attribute => 'MAX_FAILURES');
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
( name => 'PROD_LOAD_SL_FILES'
,attribute => 'MAX_RUNS');
BEGIN
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'PROD_LOAD_SL_FILES'
,attribute => 'STOP_ON_WINDOW_CLOSE'
,value => FALSE);
EXCEPTION
-- could fail if program is of type EXECUTABLE...
WHEN OTHERS THEN
NULL;
END;
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'PROD_LOAD_SL_FILES'
,attribute => 'JOB_PRIORITY'
,value => 1);
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
( name => 'PROD_LOAD_SL_FILES'
,attribute => 'SCHEDULE_LIMIT');
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'PROD_LOAD_SL_FILES'
,attribute => 'AUTO_DROP'
,value => FALSE);
END;
and this is part of the unix script get executed:
[oracle@USAC-S009 slc_prod]$ cat load_sl_files.sh
#!/bin/sh
# FILEME: /home/oracle/actual/paytment_files/load_sl_files.sh
# PURPOSE: Load SL files, email .log files
# INSTRUCTIONS/COMMENTS/ASSUMPTIONS: Two SL files will be pulled down
# MAINTENANCE LOG
# REV# DATE AUTHOR QA-ed BY CHANGE DESCRIPTION KEY
DATE=`/bin/date +%d%b%y_%H%M`
HOME=/home/oracle
export HOME
ORACLE_HOME=/u01/app/oracle/product/10.2
export ORACLE_HOME
ORACLE_SID=em
export ORACLE_SID
PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/oracle/bin:/etc:/usr/local/bin:/u01/app/oracle/product/10.2/bin:/bin:/sbin:/usr/bin:/usr/sbin; export PATH
SL_HOME=/home/oracle/actual/payment_files/slc_prod
FILE_HOME=/opt/u02/home/usair
# Call slc.sh to load files
ssh usac09.usacad.loc > /home/oracle/actual/payment_files/slc_prod/slc.sh.log <<EOT
/u01/app/oracle/slc.sh 2>&1
sleep 120
EOT
.............Hi,
The user oracle who owns the scheduler already has permissions for the mailx and the same script is able to send notifications when run manully. Do I need to set additional permissions for scheduler ?
Also the db version is 10.2.0.5.
Thanks -
ORA-27369: job of type EXECUTABLE failed with exit code: No such file or directory
Hi,
I am using the scheduler to take backup of the dev database and it was working fine. Then I added notification to the scripts and then the scheduler started failing with the following code .
BEGIN dbms_scheduler.run_job('BACKUP_DEV'); END;
ERROR at line 1:
ORA-27369: job of type EXECUTABLE failed with exit code: No such file or
directory
ORA-06512: at "SYS.DBMS_ISCHED", line 150
ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
ORA-06512: at line 1
Here' the original which has no issues
#!/bin/bash -x
echo $@
if [ -z "$ORACLE_HOME" ]; then
source /path/oracle/.bash_profile
fi
RMAN="${ORACLE_HOME}/bin/rman";
${RMAN} $@
exit $?
And here's the one which gives me the errors. Also if I run this script from command line it works perfectly fine
#!/bin/bash -x
echo $@
if [ -z "$ORACLE_HOME" ]; then
source /path/oracle/.bash_profile
fi
RMAN="${ORACLE_HOME}/bin/rman";
exec >> temp_log
${RMAN} $@
/usr/bin/mailx -s "Backup status of $ORACLE_SID " [email protected] < temp_log
/usr/bin/rm temp_log
exit $?
Pls let me know what could be the reason that the script fails with the scheduler.Hi,
The user oracle who owns the scheduler already has permissions for the mailx and the same script is able to send notifications when run manully. Do I need to set additional permissions for scheduler ?
Also the db version is 10.2.0.5.
Thanks
Maybe you are looking for
-
Erro in JMS receiver Comm Channel
Hi, I am working on a scenario File(Sender) JMS (Receiver).The input is a text file The file sender polls this input file and the file sender CC does the content conversion and puts the XML message into the JMS Queue. But in the receiver JMS comm
-
How to track the dropped login?
Hello guys, On one of our servers, we've found a login (domain\xyz12-b) missing. Tried figuring out how that got dropped, was it manually by someone, or was there a process that got it deleted. Few methods tried, 1. Event viewer- no luck 2. Sql error
-
Does anyone have any suggestions for a webcam for Ichat for the mac pro. I know some people have indicated the xbox webcam works well. Ideally I'd like one with a built in microphone since I would like to avoid having a microphone loose on my desk. A
-
Can I stop Apple's spam filters restricting genuine mail messages
I suspect that a genuine e-mail has been wrongly treated as spam by Apple's internal spam filters? The item in question is an e-newsletter from a UK preserved railway company of which I am a member. The sender has checked the log files and verified t
-
Handling in/Handling out capacity
Dear colleague, when i run optimizer profile i get message that the material does not use the handling in/handling out capacities. can any body advise how can i remove this message from the message log. Thanks Sandeep