Issue In Posting Proof Of Delivery Using Idoc using Message Type STPPOD

Hi ,
(The details I have attached in the below file.)
We are trying to perform proof of delivery with respect to a outbound delivery via IDOC using idoc inbound function module IDOC_INPUT_STPPOD.
Everything is working fine except when it is creating a new stock movement document on confirmation of proof of delivery, the newly created stock movement document is not reflecting the actual received quantity instead it is showing the the Actual Delivery quantity.
For clicking on the button - "Proof of Delivery Confirmation " (green wright symbol) and change the overall POD status as completed ( depending on this status C the stock movement document gets created) we did a custom coding in the customer exit of IDOC_INPUT_STPPOD.
The details I have attached in the below file.
I am not able to understand where I am making mistake due to which, the quantity on the stock movement document after proof of delivery confirmation is not reflecting the actual received quantity.
Can you please suggest what necessary coding changes I need to perform to make it work properly.
Regards
Saifur Rahaman

Hi Thripura,
In DELVRY03 Idoc type,there is a segment E1EDL37 containing Shipment Header Information.As a header segment,there are 6 segments under this,which contains other details.Please see the below details.
E1EDL37                        Shipping unit header
    E1EDL39                        Control segment for shipping units
    E1EDL38                        Shipping unit header descriptions
    E1EDL49                        Express Delivery Company's Tracking Connection Data
        E1EDL50                        Express Delivery Company - Additional Data
    E1EDL44                        IDoc: Shipping unit item (delivery)
        E1EDL46                        Serial Numbers HU
Regards,
VSN

Similar Messages

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Issue: "No Authorization to send Idocs with message type Orders" - IDX5

Hi All,
I am working on a File to IDoc(Orders.Orders05) scenario. The sender is PI Server and the receiver is the SAP ISR system. A technical system has been created in PI SLD for the ISR system and a Business system is added to that. The logical system created in ISR system using Tcode BD54 is added to the business system in PI. A new RFC destination is created in PI system to connect to the ISR system.
On the ISR system Partner profile is created using TCode we20 with the same logical system name already created using Tcode BD54.
When sxi_monitor is executed on the PI system, It shows checked flag on the Inbound side and Red flag on the Outbound side. And when idx5 is executed, it shows the new Idoc number and when it is double clicked, it shows the Status Text as
"No Authorization to send IDocs with message type Orders".
All authorizations have been provided on the Sender side.
Please let me know if any authorization need to be provided on the ISR system or Is this an error on any settings.
Thanks in Advance.
Stalin S.

Hi,
Check this Thread which deals with the Authorization Issue
RFC Adapter
And also check this how to check whether u have sufficient authorization to send the Idocs or not
To test the Authorization check
Double click the RFC Destination that u have created in XI towards R/3 in SM59
Select UtilitiesTestAuthorization test
By this you can come to know whether your user is having the propper authorization or not
REgards
Seshagiri

Creation of IDOC with message type INVOIC01

Hi All,
I am trying to create a new IDOC with message type INVOIC01.
When I see transaction WE81, I observe that the required message type INVOIC is available. Also in WE82 the basic types INVOIC01, INVOIC02 and INV_ID01 are attached to the message type INVOIC.
However, while trying to create an IDOC in WE19 using a message type, I get options to create against INVOIC02 or INV_ID01. The basic type INVOIC01 is not getting populated because of which all the IDOC that I create are of basic type INVOIC02.
The client wants me to create IDOCs with basic type INVOIC01.
Can anyone please help?
Thanks in advance.
regards
Nagarajan

Hi Nagaraj!
I've looked at the documentation and did not find information, which would help me. Should I use in my case z-segment to put extra lines or there is some qualifier in segment E1EDP02 (Document Item Reference Data), which triggers to another referencing (not PO or delivery note)?
Thank You,
Natalija

Batches not getting updated by incoming idoc DELVRY03 (message type SHPCON)

Hi
    I am using incoming idoc DELVRY03 (message type SHPCON) to update delivery document.I am using field E1EDL24-CHARG to pass batch data.
      However batch number is not getting updated in delivery document. I have verified aspects like batch number is valid etc.
     While updating batch number thru incoming idoc, do I need to supply some other data?
Please help.
TIA
Koustav

Hi Biswas,
I think batches are determined automatically in the deliveries while creation and thats the reason it is not getting the batch number in the delivery, if there is no automatic batch dertermination then it will update the valid batch number
also please check the batch determination procedure and the batch master in MSC2N and availability of materials for that particular batch
regards,
Santsoh

Diff bet IDOC and Message Types.

What are the difference between IDOC and Message types.
Diff between MATMAS01 ,MATMAS02 and MATMAS03

IDOCs:
- IDOC is an Intermediate Document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data.
An IDOC is created as a result of executing an Outbound ALE or EDI process.
In an inbound ALE or EDI process, an IDOC serves as input to create an application document. When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.IDOC will wait until the Remote System is Active.
Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
basic IDOC type or a customer developed basic IDOC type.
- A basic IDOC type has the following characteristics:
Name : A basic Idoc type can be assigned upto a thirty character name.
List of permitted segments: The segments make up the IDOC structure.
Hierarchy of segments : The hierarchy of segments specifies the physical sequence and any parent - child relationship in the segments.
Mandatory Vs Optional Segments : When used in the IDOC type, each segment has an attribute that defines whether the segment is option or mandatory. Minimum/Maximum range for each segment: It defines the maximum and minimum number of timesa data record corresponding to a segment cn exist in an IDOC.
-Segments : A segment defines the format and structure of a data record. Segments are reusable componets. A segment consists of various fields that represent data in data record.
IDOC Record Types:
1. Control Record : The control record contains all of the control information about an IDOC, this information basically includes the IDOC number, sender and receiver information, and information such as the message type it represents and the IDOC type.
- there is only one control record per IDOC.
- The stucture of the control record is the same for all the IDOCs and is defined by SAP.
- The structure of the control record is defined by the data dictionary structure EDI_DC40. The control record is stored in the EDIDC table.
2. Data Record : Data records contain the application data. A data record has two sections
Administrative Section and a Data section.
- The Administrative section cotain the segment name, client, IDOC number, segment number, hierarchy level information.
- The Data section of a data record is a stram of 1000 bytes where the actual data resides.
- The data record is defined by the data dictionary structure EDI_DD40.
- Data records for IDOCs stored in the EDID4 table.
3. Status Record : Status records are attaced to an IDOC throughout the process as the IDOC achieves different milestones or encounters an error. At every milestone a statu code, date and time are assigned.
- Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for inbound processes.
IDOC TYPE IS AN INSTANCE OF IDOC
Message Type: Identifies what type of information transformed between logical systems or partners.Message type is not a local object type , it is transportable.
For different applicatons we have different MESSAGETYPE.
example:
APPLICATION MESSAGETYPE
MATERIAL MASTER MATMAS
VENDOR MASTER CREMAS
CUSTOMER MASTER DEBMAS
MATMAS01, MATMAS02, MATMAS03, MATMAS04, MATMAS05 are all MESSAGETYPES ... FOR NEW VERSIONS LIKE SAP 4.7EE, SAP ECC5.0....we have to use MATMAS05 message type. for older versions like SAP R/3 we have to use MATMAS01.
REWARD ME IF THIS IS HELPFUL

Error : No authorization to send IDocs with message type MATMAS

Hi All,
My scenario is FILE-XI-IDOC.
I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
Do I need to give any authorizations on XI side or on R/3 side?
If so, what is the authorization required?
I could not find the note :837595.

You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
Solution
In transaction PFCG, extend the role of the logon user by adding the following authorizations:
Authorization object S_RFC
 Field name RFC_TYPE value FUGR
 Field name RFC_NAME value EDIMEXT, SDTX
 Field name ACTVT value 16
Authorization object S_IDOCDEFT
 Field name ACTVT value 03
 Field name EDI_CIM value ' '
 Field name EDI_DOC value TXTRAW01
 Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
 Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
 Field name ACTVT value 03
 Field name DICBERCLS value
from the note mentioned above.
Regards
Bhavesh

IDOC - same message type

hello,
I have two idoc types named MATMAS04, MATMAS05.
(to MATMAS05 i have created an extension)
they are both in the same message type MATMAS.
i need to send the two idocs to the same system.
but, in transaction WE20 when i link the message type to the system i can create only one record of the message type. in all the administration tables for IDOCs i can see that i can send to idoc types under the same essage type but WE20 prevents it.
I don't want to create a new message type.
is there a way that i can use the same message type for different idoc types?
Regards,
Roi Grosfeld

Hi Roy,
This link might help u in idoc programming
http://help.sap.com/saphelp_erp2005/helpdata/en/78/21758d51ce11d189570000e829fbbd/frameset.htm
Hope this helps,
Regards,
Nagarajan.

IDOC of message type EUPEXR

hi all,
When I run RFFOEDI to gereate IDOCS, IDOCS of message type EUPEXR and PAYEXT are generated.
I need to pass a value in a field in the control record for the IDOC of message type EUPEXR but in FM : FI_EDI_EUPEXR_IDCREF01_OUT ( which is uesd to generate this IDOC ), control record is filled and before passing this control record to MASTER_IDOC_DISTRIBUTE, I could not find any exit to change its control record.
Please help.
Thanks and Regards
Gurpreet Singh

Hi Ferry,
System checks for the IDOC version and then calls the EXIT if the versions are different .Following is the code snippet that ensures the above thing in include LBD11F0T :
Change IDOC version if target <> current version.
IF F_EXCEPTION-MSGTY IS INITIAL
 AND ( F_IDOC_CONTROL-IDOCTP <> TARGET_IDOCTP
 OR F_IDOC_CONTROL-CIMTYP <> TARGET_CIMTYP ).
 PERFORM CHANGE_IDOC_VERSION TABLES T_IDOC_DATA
 USING TARGET_IDOCTP
 TARGET_CIMTYP
 CHANGING F_IDOC_CONTROL
 CHANGED_FLAG
 F_EXCEPTION.
ENDIF. "End of if subrc = 0
Have you tested it ? Pls suggest if I am wrong somewhere.
Thanks and Regards
Gurpreet Singh

Problem In IDOCS of Message Type ORDERS05

I am Trying to place Sales Order as soon as i recieve an idoc of Message Type ORDERS05. But It gives following error when it recieves the idoc of a Purchase Order.
VKORG, VTWEG, SPART cannot be determined for customer 0000003000, vend 0000005595.
I am not Getting This Problem.
Please Help.

Hi,
Please see the link below for some information.
ABAP Development
If you find the info useful please reward with points.
regards
Aveek

No authorization to send IDocs with message type R

I'm in the process of installing some business content for a 3.5 prototype. When trying to load some master data I get the following error in the transactional RFC in the source system.
"No authorization to send IDocs with message type R"
Any clues to what may be causing this?
Any help appreciated.
thanks
Mike

Hi Michael,
the suggestion for SAP_ALL was just for testing purposes in order to see whether it works then. If security is an issue you should reduce the authorization to the ones really needed (see note).
Another security option is to make the background user a system user and not a dialog user.
Regards, Klaus

Is it possible to do message mapping using different namespace message type

Hi all,
Is it possible to do message mapping using different namespaces message types
Example :
i am having message type MT_1 in namespace http://sap.com/abc
and second message type MT_2 in namespace http://partner.com/xyz
so MT_1 can be mapped with MT_2 or not having different namespace.
Thanks

Read through my reply in this thread for Defining Software component dependencies.
Though it explains this for Improted Archives, it also holds true for Message Types to be used in message mappings.
Re: Payload Extraction
Regards
Bhavesh

RFC error "No authorization to send IDOCs with message type ..."

Hi all,
I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
Any suggestions?
Regards,
Liesel

Hi Liesel,
The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
Please check if the user id/Password that you have given has all the authorization.
Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
Regards,
Abhy Thomas

Using the same Message Type

Is it possible to use the same Message Type in several Message Interfaces?
I have BPM which is using AbstractInterface.
I created this interface based on my Message Type.
I have got mapping exeption. Maybe it is because of using the same message type.

> Is it possible to use the same Message Type in
> several Message Interfaces?
sure!
> I have got mapping exeption. Maybe it is because of
> using the same message type.
I don't think so.
Stefan

Workflow Ends in Error " No auth to send IDocs with message type ORDRSP"

Hello All,
I have created an RFC user with limited Authoprizations including WE* tciodes and a few ME* transactons for an ALE Set up. I want to make sure i would not be giving more authorizations (extensive) to this RFC user and assign Just required authorizations. So i started testing testing and the inbound IDOC ended in error with a message " No auth to send IDocs with message type ORDRSP" Message no. SR053. Is there any way to find out what is the missing authorization object for the User. Any inputs would be really apprecaited.
Br,
Sri

Hi !
Becaus alle this happens in beckgound, things are a bit difficult but solvable....
What you should do is a "Authority trace" ... as follows....:
- Go to the ST01
- Mark "Authorisation Check"
- Swich the trace on for your Workflow user
- Execute the Workflow until the error uccurs
- Go back to the ST01
- Press the "Analyze" button and see what error occurs
Dont forget to swicht the trace off... otherwise the tracefiles become realle BIG !
Regards
rainer
Some Reward poins would be nice if that helped....

Issue In Posting Proof Of Delivery Using Idoc using Message Type STPPOD

Similar Messages

Maybe you are looking for