Identify Shipment number while TPSSHT01 inbound IDOC

Hi ,
I am using TPSSHT01 Idoc to detete Shipment ,
while creating Shipment , Shipment number is created through intrenal number assignment,
My problem is that now when TPSSHT01 Idoc is coming for delete , It is not able to identify Shipment to delete ,
Can you please suggest me how the ERP will identify the shipment number for delete when the shipment number is not known to other system since number is an internal assignment to our ERP.
Do we need any enhancement for this or SAP standard functinality will do this since I have tried to delete TPSSHT01 IDOC but not able to delete.
Regards
Arushi

Closed

Similar Messages

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

Identify Shipment number in Shipment05 Idoc

Hi ,
I am using Shipment05 Idoc to create and change Shipment ,
while creating Shipment , Shipment number is created through intrenal number assignment,
My problem is that now when Shipment Idoc is coming for change , It is not able to identify Shipment to change and creating new shipment every time even when it should change.
Can you please suggest me how the ERP will identify the shipment number for change when the shipment number is not known to other system since number is an internal assignment to our ERP.
I have been told that In case of changes of an already existing ERP Shipment the reference field u2018EXTI2u2019 will be used to identify the ERP Shipment during the IDOC processing.
Do we need any enhancement for this or SAP standard functinality will do this since I have tried to change Shipment IDOC but not able to change.
Regards
Arushi

Need a E1EDT20 segment with the shipment number in E1EDT20-TKNUM
To identify your IDOC is referencing a SAP shipment number need also
E1EDT18 with E1EDT18-QUALF = 'CHA' to identify a change
E1EDT18 with E1EDT18-QUALF = 'PID' and E1EDT18-PARAM = 'TKNUM' to identify yhe IDOC is referencing a SAP shipment number.
Regards Jack

Error in number range while testing inbound idoc via we19

hi all,
i have done all configurations but while testing the inbound idoc via we19 i am getting an error 'error in assigning number to idoc'..i checked and found that the number range object for idoc is edidoc in it number interval is defined from 1 to 99
i dont think that anything is wrong with the number object..
Can u tell me how dow i eliminate this error?

Increase Higher limit the reason is when you look at current idoc number ( This idoc number already exists ) ,it will not create new idoc number.
System will get the number from SNRO Based on IDOC Object.
Just look at EDIDC and see the current idoc number.
Simple example :
I have one number - 100 ,it is already exists in database,if i insert same record to the database ,did system will accept ?
Thanks
Seshu

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

Error while posting Inbound Idocs-"EDI: Partner profile not available"

Hi,
I am getting the error "EDI: Partner profile not available" Status -56 while creating inboud Idocs.
I have done the following steps so far
1.Created IDOC basic Type and Message Type. (Custom)
2. Created process code to process the IDOC.
3. Use the FM IDOC_INBOUND_WRITE_TO_DB to create the inbound IDOC.
4. Use the FM IDOC_START_INBOUND to process the IDOC.
Is ther anything else that i have to do inorder to post the idoc sucessfully.
Thanks in advance
-Nishant
Edited by: nishant patel on Nov 13, 2009 10:35 AM
Edited by: nishant patel on Nov 13, 2009 10:41 AM

Hi,
Check in WE20 if the partner profile is configured for the idoc type and the message type. That might be the cause of the error.
Also make sure the same partner profile details are sent to the control record. Partner profile details are stored in the table EDP13.
Hope this helps
Regards
Shiva

Error while processing inbound Idoc (HRMDA_07) with FM IDOC_INPUT_HRMD

Hello,
I have a inbound Idoc of type HRMD_A (basistype HRMD_A07) which is processed by Function module (FM) IDOC_INPUT_HRMD with proofing. After processing an Idoc the status Monitor for ALE messages (BD87) tell me that my Idoc has status 53, which should be the result i would like to have.
Unfortunately when i go to transaction PA20 and check the infotypes, i see that infotype 0302 isn't created. When analyzing this problem i see that during the processing the Infotypes are posted with HR_MAINTAIN_MASTERDATA (dialog mode is 0 and luw_mode = 0 from include LRHA2F02 FORM save_pa_pb_infty) When this is done for infotype 0302 sy-subrc <> 0 the message is A complex application error has occured. This error message is placed in Export parameters
Return and Return1
of HR_MAINTAIN_MASTERDATA. When the program returns to the calling Form it checks if there is message of type E in HR_RETURN (see below) :
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
          EXPORTING
            pernr                          = ins_objects-objid       "#EC DOM_EQUAL
            actio                           = 'INS'
            tclas                           = tclas
            dialog_mode               = dial_mode
            luw_mode                  = '0'
            no_existence_check = $cross
            no_enqueue              = $cross
          IMPORTING
            return1                       = return
            hr_return                    = hr_return
          TABLES
            proposed_values    = proposed_values.
        REFRESH proposed_values.
     IF hr_return-msgty = 'E'.                           "note 984409
      CLEAR protocol_error.
      protocol_error-msgty = hr_return-msgty.
      protocol_error-msgid = hr_return-msgid.
      protocol_error-msgno = hr_return-msgno.
      protocol_error-msgv1 = hr_return-msgv1.
      protocol_error-msgv2 = hr_return-msgv2.
      protocol_error-msgv3 = hr_return-msgv3.
      protocol_error-msgv4 = hr_return-msgv4.
      READ TABLE t_hrobjinfty WITH KEY objid = hr_return-pernr
                                       infty = hr_return-infty
                                       subty = hr_return-subty.
      protocol_error-segnum = t_hrobjinfty-segnum.
      protocol_error-routid = 'create_prf_pa_pb_object'
As mentioned above, the error message is only placed in the parameters Return and Return1 and not in HR_RETURN.please read the first reply

Hi,
I think you have preety much done from your end itself .
Could you please tell me what you got in this parameters:
     protocol_error-msgty = hr_return-msgty.
      protocol_error-msgid = hr_return-msgid.
      protocol_error-msgno = hr_return-msgno.
      protocol_error-msgv1 = hr_return-msgv1.
      protocol_error-msgv2 = hr_return-msgv2.
      protocol_error-msgv3 = hr_return-msgv3.
      protocol_error-msgv4 = hr_return-msgv4.
It may help us to track down the issue in more better way .
Thanks!

How to identify mandatory fields while using an idoc

Hi
I am new to Idocs. I want to find out the mandatory fields in the segments that are used in an Idoc.
Please help.
Regards,
Lohitha

Hi Lohitha,
I dont think there is a straight forward/documented way of knowing a mandatory field within a segment, however you can use WE30 or WE60 to identify the mandatory segments in an IDOC.
I guess you will have to use common knowledge of the requirement to know/identify a field that might be mandatory. For Ex: when you are creating an ITEM on a SO, Material is mandatory etc
Regards,
Chen

Error while testing Inbound Idoc

The error message "Interface for function Z***** is incorrect*." is shown while trying to test an incoming IDOC in we19.
PL HELP!!!!!!!
The procedure followed by me was,
WE31 created custom segments,
WE30 Created custom basic type,
we81 Custom message type,
se37 function module,
we82,
we57,
bd51,
we42,
bd67,
we20,
Am not able to figure out why exactly is the error message being shown.
please tell me if a step was missed or what the possible error is, I think the parameters of function module are correct....

Hi friend,
if it is help full please give max reward point.
Standard program, RBDMOIND is scheduled or executed online to determine whether the communication was successful. If IDoc is Dispatched to destination system, RBDMOIND updates the status of the IDoc to 12 (Dispatched OK), Otherwise remains in status 03.
Two programs enable cross-system reporting:
     RBDSTATE: It reports the status of the incoming IDocs to sending system, using ALEAUD message and ALEAUD01 IDoc
     RBDAUD01: It executed on sending system to analysis the audit log and display the output as a report
IDoc Status in Receiving System          IDoc status in Sending System via ALEAUD
53 Application docu posted     =>     41 Application docu created in receiving sys
51 Error: Application docu      =>     39 IDoc in receiving sys. Status repeated
     not posted                         each time RBDSTATE runs.
68 Error: No further processing     =>     40 Application docu not created
ALE Auditing
BDM7          =>     ALE Audit: Statistical Analysis
BDM8          =>     ALE Audit: Sending the Confirmations
RBDSTATE     =>     Run on Receiving System to return Audit Message

Job cancelled while processing inbound IDOcs

Hi All,
we are sceduled job in background processing mode for the program RBDAPP01(Inbound Processing of Idocs),
but job was cancelled due to RAISE_EXCEPTION.
if i cheked in ST22 it is showing as
""The termination occurred in the ABAP program "SAPLMCS2" in "MC_SEND_MAIL".
The main program was "RBDAPP01 ".
The termination occurred in line 108 of the source code of the (Include) program "LMCS2U09""
i didn't understand why it is cancelled ?
can any one pls help me ....
regards,
suresh

Hello,
Sometimes if the Data / Right Data is not present in the IDoc, then it would not help the Standard SAP Program / Programs / Function Modules to fill-in Certain Field Symbols due to which the Short Dump might have occured.
Check the IDocs and try executing the Job again.
Thanks and Regards,
Venkat Phani Prasad Konduri

Populating serial number in the Inbound IDOC WMMBID01

I have the requirement in my project to populate Serial number via incoming idoc WMMBID01. I have created an extended idoc with a Z segment added to IDOC WMMBID01. Could anybody please let me know what would be the posting logic for this serial number.
Thanks,
Chenni.

Hi,
Maintain partner profile (Transaction code WE20) for the message type you defined in WE81 and put your process code in partner profile and check your logical system settings also in transaction SALE.
Thanks
Rahul

Inbound IDoc must trigger a workflow if shipment already exists

Hi friends, my requirement is that:
I will be getting shipment details via an Inbound IDoc into my SAP system. (IDOC_INPUT_SHPMNT) If the shipment number already exists in the system a workflow error must occur. Also the delivery number in the shipment should be validated for the shipment, if not a workflow notice should generate.
Could someone please help me in doing this.
All helpful answers will be appreciated.
Thank You

This report might help you
RSEIDOCM
Otherwise maybe in ALE customising you could create an event in a user program and use FM SAP_WAPI_START_WORKFLOW to launch your workflow.
You will have the IDOC message types coming in and the process codes which are executed so you should be able to monitor the process and take whatever action you need during the process..
(Customising -- use transaction SALE)
cheers
jimbo

Processing inbound Idoc ORDERS03 with status 51

Dear ALL
While processing inbound idoc with message type ORDERS03 i am getting a status 51 with below erros
I have maintained the data under VOE2 & VOE4 but not got the solution. We are on SAP ECC6 Version
Customer 1100 is customers purchase organization
Partner no 1109 is customers plant
VKORG, VTWEG, SPART cannot be determined for customer 0000001100 , vendor REN15D
Message no. VG204
Terms of payment in IDoc E1EDK18 have been transferred: Check data
Message no. VG202
Partner number 1109 for customer 0000001100 , partner function WE does not exist.
Message no. VG140
Regards
Arun

Hi,
Vendor 100002 is not maintained in your system. Maintain the same or use some other vendor which is there in your system.
You should be able to post the document.
Regards,
Lalit Kabra

Non English characters conversion issue in LSMW BAPI Inbound IDOCs

Hi Experts,
We have some fields in customer master LSMW data load program which can
contain non-English characters. We are facing issues in LSMW BAPI
method with non-English characters Conversion. LMSW steps read and
conversion are showing the non-English characters properly with out any
issue. While creating inbound IDOCs most of the non-English characters
replaced with '#' and its causing issues in creating customer master data in
system. In our scenario customer data with non-English characters in
the first name, last name and address details. Any specific setting
needs to be done from our side? Please suggest me to resolve this issue.
Thanks
Rajesh Yadla

If your language is a unicode tehn you need to change the options like IN SAP you need to change it to unicode in the initial screen Customize local layout(ALT F12) options 118 --> Encoding ....

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving 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 XI towards R/3
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 Inbound 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 Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
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
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Identify Shipment number while TPSSHT01 inbound IDOC

Similar Messages

Maybe you are looking for