Generate multiple idoc's from the single application doc(Sales order)

Hi All,
Iam working on a requirement where i have to generate multiple idoc's from a single sales order based on sales org, division on header data and plant at item level, if somebody please let me know how to proceed with this requirement.
Thanks
Kashif

Hi,
You can create a Z-program and call Function Module MASTER_IDOC_DISTRIBUTE.
You can make a call to this FM to send the Idoc as many times as u have plants in your Sales Order.
You can call FM IDOC_OUTPUT_ORDRSP to fill the IDoc structure.
Then u can keep the materials of only that plant for which u want to pass on the information.
Thanks,
Utsah Garg.

Similar Messages

How to generate multiple idoc's from single appl document

All,
Iam looking for a way to generate multiple idoc's from single appl document (sales order). Based on the plant details on line items in the sales order i have to generate multiple idocs, i.e., send one idoc to each plant entered in sales order line items. any help will be appreciated.
Thanks

Hi,
You can create a Z-program and call Function Module MASTER_IDOC_DISTRIBUTE.
You can make a call to this FM to send the Idoc as many times as u have plants in your Sales Order.
You can call FM IDOC_OUTPUT_ORDRSP to fill the IDoc structure.
Then u can keep the materials of only that plant for which u want to pass on the information.
Thanks,
Utsah Garg.

EDI Output type generating multiple IDOCs

Hi All,
For one of the Business requirement we have created a Delivery EDI output type and output type is processed via Report RSNAST00 in a batch job.
The delivery document shows only one output type prcossed still, mutiple idocs are being sent out for this Delivery.
RSEOUT00 is being used to process outbound IDOC.
Any pointers toward this abnormal behavior shall be helpful.
BR,
Anshul
PS - We havent implemented change Pointers

Okay, so you have one output record in the delivery document generating multiple IDocs.
Compare the control records of the generated IDocs. Do they have the same Basic Type, Message Type and recipient Partner Number?
If yes,
1. Check for multiple background jobs running RSEOUT00 at the same time. Seems unlikely, but this is easy to check and eliminate as a possible cause.
2. Step through the program RSEOUT00 as it generates the output type for one delivery document. Perhaps something is happening in a user exit that inadvertently results in replication of the IDoc.
Otherwise, the process code that gets executed by the output type in the delivery document is, for some reason, generating additional output. I donu2019t know of any standard output process code that does this, but it could be deliberate (by design). If you are sure that it should NOT happen, then step through the code and look for a mis-behaving user exit.
Regards,
zKen

Convert multiple lines for same material into a single line in Sales Order

Our company has a requirement, they want if there are multiple lines exist for the same material in sales order and purchase order then it should become like one single line.
10    35712 5pcs
20   100885 10 pcs
30   35712   10pcs
Now our requirement is that should become a single line like this
10 35712 15pcs.
I will   Text Removed.
Regards,
Khawar
Message was edited by: G Lakshmipathi
Please dont add such text in your post

Now our requirement is that should become a single line like this
Where? Meanwhile, I hope, you would have searched in SCN / Google before posting as it is a basic question and needs to be locked. If searched, specify clearly what efforts you took to find out solution to your requirement.
G. Lakshmipathi

Splitting multiple IDoc XML files into single IDoc messages for R/3

Hi all. I have a problem splitting IDoc XML files coming in to XI. I currently have an interface that takes in single store sale IDoc transactions (type WPUBON01) in an IDoc XML file. I then have some complex graphical mapping on the IDoc before sending to R/3 via the IDoc adapter. This works fine. However, we now wish to include multiple sales in one file i.e. many WPUBON01 IDocs. I could use message splitting to do this BUT the mapping is so complex, I do not wish to have to change it to enable the processing of many IDocs in one file instead of just one.
What I want to do: have one mapping splitting a multiple IDoc XML file into single IDoc messages and then another taking these single messages as before and performing the mapping. I cannot find a way to do this in one interface; the main problem I'm having is getting XI to split the multiple IDocs into many single IDoc messages within XI itself. I'd be very grateful for any advice on the best way to do this.
Thankyou.
Stuart Richards (Halfords, UK)

Bhavesh,
Thanks again for a clear explanation... I'm moving forwards but still struggling. I've been on this all afternoon today (after a break on other things) and just cannot get my message to split properly (though the SOAP adapter problem I had earlier is now fixed!). If my initial IDoc XML file contains this format:
<WPUBON01><IDOC>....</IDOC>
<IDOC>....</IDOC>
<IDOC>....</IDOC></WPUBON01>
.. I'm not sure what the cardinaility on the first message mapping and interface mapping should be. I'd have thought the source interface would be 1 and the target would be 0..unbounded but this isn't working. I'm trying different things but I get different errors each time. Currently, I have the above cardinality in my first interface and I'm passing in the following data:
<WPUBON01><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832292</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160633</VORGZEIT><BONNUMMER>1001</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1001</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832293</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1002</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1002</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832294</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1003</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1003</ZUONR></E1WPB06></E1WPB01></IDOC></WPUBON01>
In the message monitor, I get a chequered flag. Great. However, I get the dreaded error 500 in the SOAP receiver comm channel:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Exception caught by adapter framework: SOAP Error
Delivery of the message to the application using connection AFW failed, due to: SOAP Error.
Any ideas as to what this might be?! I'm getting there.... if I get a solution out of this, I promise to write the blog myself!
Cheers
Stuart

Can't create multiple dependent LOVs from the same bind variable

Hi all,
I'm having difficulty creating multiple dependent LOVs from queries based on the same bind variable in my JSF application (JDev 10.1.3.1). Basically I have a static LOV in a af:selectOneChoice component from which users select a value which then becomes the bind variable value for two separate queries that generate two different dependent LOV. Having developed the code along the lines of Steve Muench 's blog (http://radio.weblogs.com/0118231/2006/04/03.html#a685), the first dependent LOV works really well. The first dynamic LOV gets refreshed whenever the list from the static LOV changes, and I can execute other queries based on the values selected.
The problem arises when I want to create the second dynamic/dependent LOV that has the same bind variable based on the same selected value from the static LOV. Here I would also like the functionality whereby the second dynamic LOV is also refreshed after the selected value in the static LOV changes. Thinking that all I had to do was replicate the methodology used in creating the first dependent LOV, I created the second iterator, invokeAction and other binding components in the PageDef. The executable section now looks like the following:
<iterator id="SelectStaticQueryViewObjIterator"
 Binds="SelectStaticQueryViewObj" RangeSize="-1"
 DataControl="DMSApplicationModule1DataControl"/>
<invokeAction id="refreshDynamicQuery1BindParameter"
 Binds="ExecuteWithParams1" Refresh="prepareModel"
 RefreshCondition="#{empty requestScope.VariableChanged}"/>
<iterator id="SelectDynamicQuery1ViewObjIterator"
 Binds="SelectDynamicQuery1ViewObj" RangeSize="-1"
 DataControl="DMSApplicationModule1DataControl"/>
<invokeAction id="refreshDynamicQuery2BindParameter"
 Binds="ExecuteWithParams2" Refresh="prepareModel"
 RefreshCondition="#{empty requestScope.VariableChanged}"/>
<iterator id="SelectDynamicQuery2ViewObjIterator"
 Binds="SelectDynamicQuery2ViewObj" RangeSize="-1"
 DataControl="DMSApplicationModule1DataControl"/>I now have a problem whereby everytime I change the value of the static LOV, multiple HTML components for the same ADF component are being generated (the LOVs are refreshed via PPR). The surprising thing is that this duplicating behaviour applies to all ADF components listed after the first dynamic LOV in the *.jspx source. For example, I have a <af:outputText="Test Text"/> component created after the first dynamic LOV. Each time the value in the static LOV changes, a duplicate HTML component is created. This also applies to the 'related' second dynamic LOV which is bound to a af:selectOneChoice component - multiple dropdown lists are created. I've checked with the browser's Page Source and there are actually multiple html components being generated with their own unique ADF-generated IDs. I've tried all different options for the Referesh and RefreshCondition attibutes in the second invokeAction element but nothing seems to eliminate this issue.
Any suggestions about how I might create multiple dependent LOVs from the same bind variable that get refreshed when the selected value changes would be greatly appreciated.
Thanks
George

Hi all,
Just updating the thread on how I've overcome this issue. As it stood the manner in which I was trying to solve my use case, as described above, was creating an absolute mess. Then with a blank sheet of paper I quickly realised that a much simpler solution would be to create a whole series of master-detail VOs and build my components around them. Thankfully I haven't had any issues going down this path as yet.
Cheers
George

Running SCOM ACS in multiple customer environments from the same SCOM management group ?

We are currently monitoring multiple customer environments from the one SCOM management group and are looking at possibilities of using ACS for auditing.
Is this technically possible ? Does the ACS collector service need to sit on the customer side ? could it be installed on the same server acting as the SCOM gateway server ?

Hi,
The number of ACS forwarders that can be supported by a single ACS collector and ACS database can vary, depending on many factors, such as the number of events that your audit policy generates, the role of the computers that the ACS forwarders monitor.
If your environment contains too many ACS forwarders for a single ACS collector, you can install more than one ACS collector. Each ACS collector must have its own ACS database.
An ACS Collector must be installed on computers running Operations Manager management server and for security reasons, it must also be a member of an Active Directory domain.
More details please refer to the article below:
http://technet.microsoft.com/en-us/library/hh212908.aspx
Regards,
Yan Li
Regards, Yan Li

Getting valid idoc number from the sales document

hi,
Iam sending the code for getting the idoc number from sales document.
but iam not getting the result.
please see the code and correct the code so that i will get the idoc number from the sales document.
tables edid4.
data l_docnum like edid4-docnum.
parameters:p_vbeln like vbak-vbeln.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
exporting
 input = p_vbeln
IMPORTING
 OUTPUT = p_vbeln
select single docnum from edid4 into l_docnum where sdata like '&p_vbeln&'.
if sy-subrc = 0.
write edid4-docnum.
else.
write ' the record is not found'.
endif.
it is very urgent..............
thanks in advance......

See the below code :
report zxyz.
tables edid4.
data l_docnum like edid4-docnum.
parameters:p_vbeln like vbak-vbeln.
data sdata like edid4-sdata.
start-of-selection.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
exporting
input = p_vbeln
IMPORTING
OUTPUT = p_vbeln
concatenate '%' p_vbeln '%' into sdata.
select single docnum from edid4 into l_docnum
 where sdata like sdata.
if sy-subrc = 0.
write edid4-docnum.
else.
write ' the record is not found'.
endif.
Thanks
Seshu

No Idocs arrived from the source system.

Dear All,
Please read this issue carefully.
Error Message is that
"No Idocs arrived from the source system."
In the Details Tab:
Trasnfer( IDOCS &TRFC):Missing Messages or warinings.
Request IDOC:Application Documnet posted from BW side and it is green..There is a request BW IDOC number sent to R3.
Where as an InfoIdocs 1:Sent not arrived :Data passes to the Port is ok.
Here i can see there is one idoc frm OLTP R3 side ansd no incomming idoc for BW side
I went to r3 side bd87 and found that idoc is posted well with status 53.
This is happing in Bw for each iinfopcakage is running?

Hi,
go through this link...
[https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=noidocsarrivedfromsource+system&adv=false&sortby=cm_rnd_rankvalue]
System.-> Check RFC connection and clear/process stuck IDOCs.
Idocs Missing or No Idocs arrived from source
For this check the TRFC que(SM58).If any Idocs r strucked up there execute them manually.checkin sm58 transactions, you can check the status of your Idocs using BD87 in R/3. Idocs may not be processed because of load on system. You can process them manually from context menu.
And go to BD87 to process the idoc's ..
check which idoc has to process...select the idoc and click process ..Then It will push the data into the data targtes,
Hope it will help you;
regards,
NR

R/3 connection to BIW - No Idocs arrived from the source system

Question,
Hi Team,
I have issues during loading attribute data from R/3 source system to BI,
I go to the path
Data Warehousing Workbench - Modeling window. In the DataSources view, my application component Group ##. On my DataSource i Create Info Package and save it,
Later I select the following options
Full Update = select
On the Processing tab page, select only PSA.
On the Schedule tab page, choose Start Data Load Immediately and start the data load.
Till here everything is in active version and saved, and connection to the source system is active and working fine.
However when I do loading I received following messages, what I observed in Monitor window,
Data was requested OK
Request still running
Diagnosis
No errors found. The current process has probably not finished yet.
System Response
The ALE inbox of BI is identical to the ALE outbox of the source system
or
the maximum wait time for this request has not yet been exceeded
or
the background job has not yet finished in the source system.
Current status
No Idocs arrived from the source system.
When I go to detail tab, under transfer section, I receive the following message
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
But when I actually go to PSA maintain section and select data and no of records, I can see the that data is loaded into PSA section,
But when I chose to run the transformation I donu2019t get data here,
Kindly help me to resolve this issue,
Regards,
BluSKy

Hi,
the BIW i am using , its compact BIW, which is in EXI, and i execute transaction /nrsa1 to go biw development workbench,
i am not sure about transactions settings about r/3 side,
could you plz throw some light on this issue,
regards
blusky

Is the way to retrieve the deleted pages from the database application

Hi,
I was just deleted the pages from my database application wizard. Now, i want to retrieve the deleted pages, can you help me to retrieve those pages.
Thankyou.

Halloween can be a scary time -- especially if you Oops your APEX application. Of course you can't travel back in time but through the miracle of flashback, you may be able to get the APEX appl. back to where it was when. I tried these approaches and was successful with them.
*** This assumes flashback is running on the APEX schema(?). Your abiliy to go back a given number of minutes (or hours?) will depend on whether the saved values still exist in the database. ***
A) If you modify a page and want to go back to what you had, say, about 30 minutes ago.
1) Under the Utilities button (on that page), select History.
2) Determine how far back in time you want to go by examining the list of editing changes displayed.
3) Do a page export of that page (also under Utilities) and fill in “As of __ minutes ago”.
4) If you don’t want to lose what you've got on the “damaged” page, copy it to another page number for now.
5) Import the exported page file.
6) Check if you got back what you wanted.
7) If not, try an earlier (or later) time and have another go at it.
B) If you deleted the wrong page in the application!
1) Assuming the last thing you did was this deletion, export the entire application filling in “As of __ minutes ago”.
2) Just to be careful, import the file to a different unused application number. Don't overwrite someone else's application.
3) Copy the deleted page from the new application back to where you need it.
4) Clean up by deleting the unneeded application.
C) If, "Doh," you deleted the wrong application!!!!
1) Are you able to retire? If no, then proceed!
2) Create a minimal application (with a single page) with the same number as the one deleted.
3) Export the application filling in “As of __ minutes ago” with an appropriate number of minutes.
4) The export file should contain the code you need to restore.
5) You can inspect it with an editor.
Look about line 25 for" Pages: <number>".
For specific pages look for "page_000nn".
5) Import the file to the same appl. number. You should get everything back!
YMMV: Your mileage may vary!
I'll take my leave with the words of that immortal song:
"Yes. Oops, Oops, Oopsie! Good Bye. But Oops, Oops, Oopsie. Don't Cry."
(With apologies to Ted Fio Rito, 1900-1971.)
Howard

Multiple log4j.xml files for single application.

Hi All,
How to use multiple log4j.xml files for single application?
I do have a pluggable application modules. ie, If I add a jar I will get some functionalities. Like that i do have many jars.
Log4j.xml also will be present in that jar only. So if I add multiple jar files like this, I will get multiple log4j.xml files. What should I do?

Each logger can have its own file I think. Check the log4j documentation.

Calling multiple script logics from a single package

Team- How do i call multiple script logics from a single DM package...?
I know its possible and have seen a prototype but cant recollect or find it on sdn...
Thanks for your time.
Vishal.

Hi,
You can create a master script logic which will include all the other script logics using the *INCLUDE command and call this master script through your DM package.
Another way is to have multiple tasks in the process chain which is calling a script logic. You can pass separate script logics to each of the tasks.
I would prefer the first option
Hope this helps.

Creative Cloud for Students: Adobe Manager Application ask me to subscribe the single application or entering a serial number that I have never been provided. [was: URGENT URGENT]

I subscribed Adobe Creative Cloud Students on 2/12/14 , but once the trial version is end, Adobe Manager Application ask me to subscribe the single application or entering a serial number that I have never been provided . I consulted all the suggestions from Adobe , without finding a solution . In the event that the problem is not solved I will be forced to cancel my subscription .

This is an open forum with a mix of program users and Adobe staff, not Adobe support... you need Adobe support
Adobe contact information - http://helpx.adobe.com/contact.html may help
-Select your product and what you need help with
-Click on the blue box "Still need help? Contact us"

Creating a HTML page from the J2ME application

Hi,
I am developingan application in J2ME. Can anyone of you out there, help me whether there is any way I can generate a HTML page from the application.
I have the data but I don't know ho to create a HTML page from a J2ME application.
Any document or any code will prove handy.
Thanking in anticipation.
Ashish

When you say that "you have the data" you mean that you have HTML code data(<html><body>Hello World</body></html>)? If yes you should create an algorithm that "read" html tag and display text in the appropriate layout/font/size/color...
A solution could be simplify your HTML code (server side), so you can easly "decode" and display text.
Giovanni
Italy

Generate multiple idoc's from the single application doc(Sales order)

Similar Messages

Maybe you are looking for