A Uncanny Problem with IDoc Outbound:

Hi,
I meet a problem When outbounding a Z idoc: a field in a segment has no value (While according the trigerred FM logic, should not space): segment structure: matnr lorvm sprat1 ... vkorg
the data source is from table MVKE. Some times the field 'VKORG' is space in IDoc created using FM 'MASTER_IDOC...'.
It is uncanny one as 'VKORG' is a key field in a record, it's value always is not space!
Why the issue occurs?

Hi Nitzan,
ALE does not do these checks! Maybe you can do some coding in ALE-Userexits do achieve this with your own ABAP (i.e EXIT_SAPLRHA0_005).
Where does wrong data come from? Can't it be checked before sending to targetsystem.
What shall ALE do with data, which it cannot insert? Shall it stay there in ALE-input without ever been worked up?
Regards
Herbert

Similar Messages

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (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.
2) Create Port (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 SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

Problem with idoc DEBMAS

Hi everybody.
We have a problem with idoc DEBMAS.
This idoc is sent from R3 to PI throw change pointers then the idoc is field only with the data modified in the master custumer.
We need the information fill it in the segment /IDOC/E1KNA1M/E1KNVVM to determine the receiver determination but this segment is not always sent.
What can be done in R3 to send always this segment.
We dont want to sent the whole data but always this segment.
Any idea???
Thanks a lot!!!!!

Hi,
As E1KNVVM segement is not mandatory, when you are triggering IDoc based on change poitner data might not populted in the E1KNVVM segment until some sales data is changed.
if you need that segement always just copy the Idoc type and make it mandaotry field.
otherwise yoy can populate some fields like STDVRS with the reruried constant and can use in your receiver determination.
Regards,
Suresh

Problem with IDoc for an outbound delivery

Dear All,
I am facing a problem with the IDoc defined for an outbound delivery.
Scenario:
Implementation of a small enhancement for an IDoc (DESADV, DELVRY01) created for an outbound delivery (in VL02N).
What I did:
I implemented the EXIT_SAPLV56K_002 exit in the V56K0001 enhancement, activated in SMOD, assigned V56K0001 component in CMOD and acivated it. Then I put a breakpoint on the ZXTRKU02 include. For me everything in SMOD and CMOD looks OK.
I have also created a partner profile, port, outbound message config. (message DESADV, basic type DELVRY01, application V2, output message type LAVA, process code DELV. function module used for this process code is IDOC_OUTPUT_DELVRY).
What I can do:
I can issue an IDoc message, it looks ok and contains the standard data.
Problem:
It seems that the enhancement does not work. Finally I put there only one line of code to avoid a program bug and just to check . The system does not stop at the breakpoint (set on the ZXTRKU02 include in the EXIT_SAPLV56K_002 exit).
Am I using the proper exit? I appreciate any suggestions.
Thanks,
Grzegorz Skorus

Hello Grzegorz
Not an expert on this, but noone is responding so I thought let me try and help you. You seem to be doing the right things as mentioned in OSS note 1498409.
Firstly since this can be called form Shipment Idoc also, you may need to make a differentiation by the interface parameter 'MESSAGE_TYPE' or segment name. See the attached OSS note, though it belongs to older releases, it may help you.
Also help says 'The callup of this function module is programmed for each enhancement of the internal table for the IDoc (in other words, when you add an extra segment'. So may be you need to add an extra segment/field to make it work.
Futher the user exits are replaced by BADIs. May be you should use exit_badi_v56k.
Hope this helps and others will pitch in.
1498409 - Valuation Type unavailable when creating deliveries using IDOC
631913 - Exit after formatting delivery IDoc type DELVRY

HR Programming : Problem with IDOC HRMD_A

Hello ,
We use Idoc HRMD_A for transferring PA records from
one R3 system (ECC5) to another R3 system (46d).
We have a problem - The Idoc doesn't check the data
inserted against the database check tables and
inserts wrong values into the target system database.
(At least that what has happened when we transferred
wrong value of MASSN in 0000 records).
Is there something we can do ?
Maybe - Some flag we can sign in order a check against check tables will be done ?
Is it a problem with this IDOC ?
Thanks .
I appreciate any help.
Nitzan S.

Consultancy note 134085 :
"Ultimately you are responsible for consistency of this data. SAP saves this data directly on the database without checking the single fields and consistency of the data records (time constraints check, writing change pointers, value check) because the consistency for an R/3 - R/3 lingage is of course ensured."
The IDOCs were intended for R3->R3 data replication, and not for data loads/interfacing. Since you're having problems, I'm guessing in addition they require the same SAP version as well.

Problem with IDOCs

Hi all,
I am trying to send MATMAS IDOCs to Siebel server using plain HTTP Reciever Adapter.I am able to see success messages in SXMB_MONI for Some IDOCs I mean where the IDOC have minimum segments which does not contains mandatory data.
In some IDOCs it is showing the following error which includes all the relavant fields for Siebel.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Internal Server Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 500 reason Internal Server Error explanation Internal Server Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any ideas on this ???
Sekhar

Hi all,
sorry for the confusion...problem with the IDOC data only..
Sekhar

Problems with deleted outbound deilverys

Hi all,
I have the following problem with a deleted outbound delivery. The issue is that a sales order was created and a outbound delivery was assigned to this sale order, but somebody deleted the outbound delivery, unassigned the corresponding material and the shipping person assigned this outbound to another sale order believing that there were still plenty of material to cover both sales orders.
The help needed here is how do I know which user deleted the outbound delivery is there a record for that??
I'll appreciate your help a lot.
Best Regards,
Erik Espinosa

Malice is seldom behind stuff like this, from my experiences.
Prime candidate is human error (possibly with an attempt to fix it, which also includes hiding it...).
=> Send the sales folks a mail with the order number and description in it and ask them whether any of them know about it or are aware that an error might have been made. This gives them the opportunity to realize the implications of their mistake, or "own up" to it.
Depending on how your system is integrated and how many "cowboy" developers you had / have around, faulty config and even naive user-exits cannot be completely excluded.
=> Hard to find (better to prevent), but doing a where-used-list on the related VK* tables to see whether any Z-programs turn up is a start.
Either way, with the sales order number, you should be able to find the user context which performed these actions via the business change documents.
=> Take a look at the SCD* transactions, and the CD* tables.
If it was a batch user at midnight... then see "Hard to find..." above.
Cheers,
Julius

Problems with Idoc Artmas03 to create a variant

Hi everyone, We had created a individual material through Idoc artmas03, we need to create a variant, we have problems with some segments E1BPE1VARKEY & E1BP1AUSPRT, our problem is how to create a variant & how to full this segments, is this correct from Idoc Armas03? or is it necesary another Idoc? Some have some examples, thank you very much
Best Regards from Mexico,
Atte Israel

Guys,
I am running mozilla firefoz 5.0 and the only option that is coming to me is to create folder in CA.
even though SAP recommands IE and allows portal from Mozilla, the later seems to have serious issues with Portal.
I remember working with several versions of mozilla, sometimes you right click, all option will come but you will be unable to choose options coz when u bring cursor to them they will skid here and there..
I hope no SAP note elobrates this as of now.
Ankur

Problems with IDOCS

Hi everyone!
I'm working with IDOCs and I am having the following problem:
I'm modifiying a specific standart IDOC (DELVRY03), adding a new structure called ZSTRUCTURE. When making an example to create the IDOC I am not able to find the new structure that I have just created in the IDOC.
Does anybody know why? Maybe the structure is empty, is this a problem?
Thank you very much.
Regards

hi,
   I dont think u can direct modify sap standard idoc type.
   Instead u can go for Idoc extension.
   Create structure ie segment u want to add say EDIT->set release
    and in we30 choose extension create zobject type with extension as standard idoc and choose EDIT->set release
   and goto we80 add msgtype,Basic idoc type, extension.
   I think this will fix ur problem.
Regards
Shanmukhi

Mapping Problem with IDOC HRMD_A05

Hi All,
When i am mapping source structure with IDOC HRMD_A05 i am getting Mapping not sufficiently defined...
The idoc is used to change the address of employee(infotype 0006)..
my source structure is
EMPADDR_MT
   EmpAddr1
     Trans_INFTY *
    Address1
      AddressType *
      PERNR       *
      EFdate      *
      Addr1       *
      Addr2       *
      ADDR4       *
      City        *
      Country     *
      state       *
      Postalcode *
the fields to be mapped
So can any one help me out what r fields to be maintained for <b>HRMD_A05</b>...
Regards,
Sridhar
Message was edited by: sridhar reddy kondam

All the required fields & segments(shown red in mapping editor or min occurence:1) of idoc need to be mapped.If any of the fields are not available in your source for mapping..map those fields with empty constants using constant option of the mapping editor.

Problem with automatic outbound IDoc creation

Hi all!!!
I want to configure an IDoc to be created when an Installation (IBASE) is saved.
To do this, I use the IDoc type CRMXIF_IBASE_SAVE01, assign a message type, link with the FM APPL_IDOC_INPUTM to create the IDoc, create a partner profile, create the process code and set on the message type.
After this, when I create an Installation, Must not the IDoc be created?
Is the process correct or lack some step?
Thanks and regards,
Manuel.

And, on the partner profile, I can´t set the process code on the outbound parameter because the field doesn´t appear.
I think this could be the error.

Problems with processing outbound IDocs in background processes

Hello everybody,
I have a question for working with ABAP-PSS Ports.
The behvaiour is that I want to send master data, for example customers, to a function module. This function module works like an converter which process and writes the files in the filesystem.
Following situation:
- I have defined a partner System with different message types, for example DEBMAS and everthing what is necessary to replicate data to partner systems.
- I have defined also a Port like ABAP-PPS Port for calling my own function module.
- If I runs the program I process only 50 Idocs per process because otherwise i can happen that there are to many look entries in the system and the job crashs. (For example all customers are around 50000 Idocs).
Now my problem is that the worker for processing idocs starts each process in the foreground and in parallel.
But this is very strange! Because then all dialog processes are reserved and the system will be very slow!
How can I configure the Port or what have I to implement in my fucntion module to start processing in background (this is the very important point) and maybe allow the program only to use one or two process at the same time?
I have found on the function module EDI_DOCUMENT_CLOSE_PROCESS which I the parameter "Background". What thas this mean? I have set B for this but it has no effect!
Regards
Christian

I know that for inbound interface it is possible to define if in foreground or background and if parallel processing is allowed.
Who knows how I can do this also for outbond?

Problems with idoc ORDERS05

Hi experts,
I created a new Z segment for idoc ORDERS05 and it works fine. This idoc is generated whenever a PO is created or modified. But if the PO has locked or deleted items, there is no segment for this items in the IDOC. Should I modify any code or something in SPRO??
Thanks in advance,
Maria

Hi again...
I'm trying to make a copy of the standr FM IDOC_OUTPUT_ORDERS because I think it may be easier to add the segments I need. I have also created in tx. WE41a new operation code ZME10 with my new fm. An in tx. WE20 I have assigned ZME10.
The problem is when I run ME9F i get this error:
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',
was neither
caught nor passed along using a RAISING clause, in the procedure
"NEW_DYN_PERFORM" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The program "RSNASTED" contains the CALL FUNCTION statement.
The name of the function module to be called is "ZIDOC_OUTPUT_ORDERS".
but "ZIDOC_OUTPUT_ORDERS" cannot be found in its function group.
Any idea ??
thanks in advance !

Problem with IDoc filtering in the distribution model

Hello Experts,
We are using a distribution model in which we have set filters as like the following
Filter Group 1
Plant : XYZ
Sales Org: SAP1
As far as the documentation says this Condition should work with AND logic between Plant and Sales Org
(i.e ~ Plant XYZ and SO SAP1 ) but the IDoc gets created even if any one of the condition is met(looks like working in OR logic).
How to achieve the AND filtering between the different objects.
Would appreciate your kind help.
Thanks in advance.
RGds,
Vasanth.

> Jakub ~ Yes I checked the generated IDocs(classified pertaining to my Model)for my model alone and that's where we are facing this problem
So that's the filtering problem.
I would check in which segments are the "filtering objects" located (BD59) and whether it is a mandatory segment. If it is a mandatory segment - IDoc should not be created. If it is an optional segment - this segment and its subsegmets will be filtered out - but IDoc will be created.
> ~ Do we need to apply some SAP Notes to avoid this problem ?
> But why the filter should behave in OR fashion ? I do not understand.
I believe that Sachin meant that the logic is:
Filter Group1 OR Filter Group 2 OR ... Filter Group N
Filter Group 1 Object 1 AND Filter Group 1 Object 1 ... AND Filter Group 1 Object M
Filter Group 1 Object 1 Value 1 OR Filter Group 1 Object 1 Value 2 OR ... Filter Group 1 Object 1 Value L
regards,
Jakub

Problem with Idoc segment maximum length

Hi friends,
We are now creating a new Idoc type. We have started to create the first segment but we encountered a major problem.
The problem is that we have a field of 4000 characters but the limit of all segment fields together is 1000 characters.
Is there any way to change this limitation or another way to define Idoc?
Thanks in advanced,
Udi Dekel.

Hi,
When you create a segment that exceeds the max length, SAP automatically creates a child segment for the exceeded length. For your problem though, you can create 4 segments of length 1000 each and split the data in these 4 segments and then concatenate the data later in the idoc processing function module. On the other hand if it is an outbound idoc, you can ask the receiving system to do the same.
Best regards,
Advait

A Uncanny Problem with IDoc Outbound:

Similar Messages

Maybe you are looking for