IDoc output type not getting configured in IDoc-File scenario

Hello
I am having IDoc to file scenario where I want to post Delivery Document to legacy system. For this I have configured following EDI configuration for Delivery through NACE transaction
1] Created output type
2] Created partner function as EDI LS for this output type
3] Configured RSNASTED as Processing Routines for output type
4] Included this output type in the Header output procedure
5] Configured XI system as the partner in partner profile with appropriate Message control
Still when I attempt to include this output type in the Delivery it gives me "Output for partner could not be configured". The detail message says "In Customizing, the 'CannotBeChanged' indicator has been set for output type".
I checked in SPRO but could not find such flag.
Does anyone had came across such output type configuration.
Thanks in advance.
I know this question might be not appropriate in XI forum as it comes under EDI but it has become necessary for XI profs -:)
Regards
Rajeev

Hi,
Please check the following
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
Copy NEU to ZNEU or YNEU
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type ZNEU or YNEU.
G.Ganesh Kumar

Similar Messages

Business service NOT getting configured from jca file in Windows 7

I am faced with a problem in Windows 7.
In one machine with Win XP as OS, when I create a business service from a JCA(.jca) file, the Endpoint URI gets configured automatically with jca://<jndi name>/... and having protocol as jca.
But, when I do the same in Windows 7, the endpoint URI is not getting configured neither do I find a jca option in protocol so that I can configure it manually.
The probable reason I sense, is that some files(may be jar or others) are not getting the acccess required by OEPE.
Any suggestions, which jars or files are required for the configuration to be correct??? I mean for the JCA protocol to come up ??

I could create a JCA business service on windows 7 64bit without any issues. Can you follow below points and let us know the result -
1. Make sure that you are running eclipse as administrator. right click on "eclipse.exe" and select "Run as administrator"
2. Make sure that file $OEPE_Installation_Dir\dropins\oracle.osb.ide.link has a valid OSB home entry like below -
path=E:/ofmw11g/mw/Oracle_OSB13. Make sure that below directory exists -
$OSB_home\eclipse\plugins\com.bea.alsb.transports.jca_1.1.0
For e.g. - my setup have E:\ofmw11g\mw\Oracle_OSB1\eclipse\plugins\com.bea.alsb.transports.jca_1.1.0
Regards,
Anuj

Output type not getting saved in the PO

Hello Team
we are facing one issue where output type is not getting saved in the PO.
we give one output type and than save it , after going back to the PO we see that it is not there.and no output issued
the PO is released properly and there is no issue , any idea what could be the reason for it

Hi,
Check in SU3 t.code, did check box selected u201CDelete After Outputu201D in Spool Control segment in Default TAB
Also check Partner Function VN maintained in Default values TAB in NACR--- > EF Application for your output type
Cross check partners {VN, PI, GS) are assigned to your PO output type in Partner Roles per Message Type
Regards,
Biju K

Output type not getting defaulted in PO

Hi.....
I have configured output type as printout for purchase order, i have set the default value for message type NEU, even than when i create a PO system is not picking the message type NEU..
i have also mainatined condition record in MN04 for the purc. document type..
any other setting need to be maintained....
Kindly suggest....
Regards
Sarfraz

Hi,
Please check the following
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
Copy NEU to ZNEU or YNEU
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type ZNEU or YNEU.
G.Ganesh Kumar

EDI Output ZB00 not getting determined in case of Split Deliveries.

Hello All,
A very Good Morning to you,
Hope you are doing good,
We have come across one critical Issue where the EDI Output ZB00 Dispatch Advice is not getting determined in case of few Split Deliveries in PROD.
Issue : On a daily basis our Client is generating Split Delivery Process used for some specific customers only.
These specific customers we are maintaining in ZPARAMS Table. The Flow of the Process is as below.
Sales Order -->Parent Delivery ZLF--> Split Delivery ZLS--> Invoice ZF2.
First the Sales Order ZOR is created through VA01 or EDI.
This ZOR is processed via ZVL10A to create parent delivery ZLF.
Once the parent delivery ZLF is created an Outbound IDoc SHPOD gets triggered which goes to the Distribution Centre Technicolor UK to check the confirmed qty and materials that needs to be delivered.
Once the Quantity is verified and confirmed from DC an Inbound IDoc SHCON interface SAP.
This Inbound SHPCON IDoc checks the entry in ZPARAMS for that customer. If the entry is found it creates one more Split Delivery ZLS doing picking and post Goods Issue in one step. This is the point where the ZB00 output is determined automatically in ZLS Delivery and processed successfully immediately.
After that the Normal Invoice ZF2 is created.
We have given the process flow details in the attachment along with Functional Modules used by the EDI Team.
Now the Issue we are currently facing on a daily basis in PRD Out of the Total Count of ZLS Deliveries in few of ZLS Deliveries ZB00 Output is not getting determined at all which is causing a huge revenue loss. For remaining ZLS Deliveries it is getting determined correctly and processed.For Split Delivery we have only 2 Customers.
We would like to know why this is happening in case of only few ZLS Deliveries.
As a work around we have just write one program for these disputed deliveries where it will go in VL02N of these deliveries and save it without doing any changes. This will make ZB00 determined and processed immediately.
We have even check the scenario in Quality Client no Issues at all. It is getting determined and processed successfully for all the test cases we created.
Please could you help us on this so that we can fix this critical Issue.
Many Thanks,
Farhan.

if QA system works correct
you probably need to find the difference between it and PRD client.
I guess it is a huge job.
but who does if not you?
because you have a lot of custom things included coding
also request abaper.

Output type NOT displaying

Hi,
I am creating a new Message type - zse1 to output the Purchase Order thru EDI.
I have done the basic settings, of defining the Partner profile, message type, port definiton.
But when I create Purchase Order & goto the messages tab, I am not able to see the new output type that I configured, nor can also select manually from the drop down list.
How should I make the output type to automatically show up in my Purchase Orders?
Any config I have missed out? Pls help.
regards,
pri

Hi Anne..
For congiguring the Outputtype...the steps are..
1.Define Output type ( Hope you did....)
2.Assign this in to the output determination Schema RMBEF1
3.Assign this schema into Purchase order in "Assign
Schema to Purchase Order"
4.Go to MN04
5.Enter your message type and select the Key combination.
6.Maintain all the entries and after that Select that line and
click "Communication".
7.Maintain the printer and all settings in this communication.
Now put your PO ...and defineteluy the message type will pick up Automaticaly.....
Award if solved.....
Thans and Regards
R.B.K.Kannan

Output type not determined during background Job

Hi Experts,
we have scheduled a Job to create Billing. In few of the billing documents, output type is not getting determined. Condition records are maintained correctly. This is happening only for few billing documents in spite of maintaining condition records?
Can some one help me on this issue.

shravan,
added: How do users come to know that in few documents output is not getting determined?
To check determination of output record - In VF02, give the billing document for which output was not determined.
Goto > Header > Output, check if the output has got determined.
If not then it is not getting determined.
any difference between the documents in which output is getting determined and in which not?
TW
Message was edited by: TW Typewriter

VA00 condition type not getting determined for the returns order

Hi All,
I have a case where VA00 condition type not getting determined for the returns order that has been created with respect to the billing document.
When the pricing conditions are being copied from invoice it is getting copied but later it is getting deleted in the include LV61AA42.
Note:VA00 condition type is getting deleted from the internal table tkomv[].
If any one came across this scenario can you please help me.
Request your valuable inputs

Hi,
Please check the copy control setting in VTAA.
Maintain the pricing type as "D" at item category level for the respective document type .
Hope this will resolve your issue.
Regards,
Krishna O

Error is not getting logged in error file while running dataload maxl

Hello All,
I am running a Maxl to load data in a database which is running fine but noted a weird issue that the errors are not getting logged in error file. Suppose i changed the name of data file then it should give error something like
ERROR - {Error no.} - Unable to open file {filename} which should be logged in error file but my error file is still empty.
I am using the Maxl -
import database {dbname} data from data_file {filename} on error append to "D:/Error/errorfile.err";
Any inputs please...
Thanks

Try to use single quotes and the backslash. It may depend on the operating system and /or the version of essbase used. This is an example from one of my maxls:
on error append to 'D:\Hyperion\logfiles\myload.err';
cheers, chris

GetCoreResourceModificationDate could not get path to timestamp file

Porting my InDesign CS5.5 Plugin to InDesign CS6, when I build a debug version of the plugin and deploy it to the InDesign CS6 Debug version and launch InDesign I get "PlugInData::GetCoreResourceModificationDate could not get path to timestamp file: C:\Program Files (x86)\Adobe\Adobe InDesign CS6 Debug\Plug-ins\SCC\(SCCINDDEXTRACTION V7.1.0.17 FOR CS6 Resources)\timestamp.idrc" which suggests that InDesign is expecting to find a "timestamp.idrc" file in the root of my plugin's resources subfolder. I have searched the sdk and google and have found nothing about a timestamp resource for InDesign plugins. Is my plugin resource (.rc or .fr file) supposed to include some kind of timestamp that would cause the resource compiler to generate a timestamp.idrc file?

OK, I fixed this, but not sure how.
I think the cache was corrupt.

Output type not created for outbound delivery while using SHMNT05 idoc type

Hi Experts,
Please help me to solve the below issue.
Problem:- I want to to generate an IDOC(using type SHPMNT06) once the PGI is done for an outbound delivery.
Already it is working fine when used DESADV.DESADV01 or DESADV.DELVRY07. But now the output type is not getting created when used SHMNT.SHPMNT06. I have created a separate output type ZPJ7 just as a mirror copy of the earlier output type(ZPJ6) used for DESADV.DELVRY07.
Question:- Is it possible to use idoc SHPMNT06 instead for DESADV01 or DELVRY07? If yes then what are steps to be followed?
The reason why SHPMNT06 idoc is planned:- We have a scenario to send outbound delivery to 3rd party system via XI. If the outbound delivery is for National(Not for Export) and PGI is completed then send the idoc straight forward to XI otherwise DO NOT generate the idoc, but just create the delivery. Collect all the deliveries in a transport and send it in a shipment. The shipment details can be sent using SHPMNT idoc. Now from XI perspective, if we can utlitze the same SHPMNT idoc for the National delivery(1st case) then perhaps this will require less effort. Hence shipment idoc is required to be generated when the delivery is created and PGI is done.
Also it would be great if you can advice some better way to solve above mentioned scenario.
Many Thanks,
Sanjay

There could be several reasons. Go to the document and in the extras-output check output determination analysis in the processing log.
If the output has been created successfully then you need to see your printer determination. Ask basis to check it up. If the problem is that even the print preview is not coming. Check your communication in the output analysis and ensure LOCL is selected. Any other printer will need to be configured.
If thats done already then check whether you have maintianed the condition record.
If that too is done then check whether your output type has been assigned to the output procedure and that the output type is listed in the procedure.
regds
Jude

IDOC output type configuration

Dear All,
We are integrating with another system for warehouse management and delivery note print out will be taken from third party system once delivery is created in SAP. When delivery is created, and IDOC DESDAV will be sent to third party system which carries all necessary information for delivery note.
My question is, to trigger DESDAV IDOC I have copied LALE output type and changed some setting. I have maintained condition record .
The settings are : Access Sequence : 0008, Access to condition, Send with periodically scheduled job, Tran mission medium: Distribution ALE,
Since the process is as i am sending to third party system not to a specific partner , i have deleted the partners assigned in the standard " SP" and left the field blank in partner function.
When i create delivery, this output put is appearing twice in Determination analysis, and not appearing automatically. when i maintain manually, system is asking for partner(SP).
How do i maintain the third party system as my partner. I have two questions here
1) Output type is not appearing in Delivery
2) should i maintain the third party system as sold to party SP or LS(logical system)
Kindly guide me.
Note: I have maintained the output type in IDOC - DESDAV and when IDOC triggered manually, IDOC is getting generated.
Regards
Fazal

Hi Santhosh,
I am able to trigger IDOC now and below are my setting.
Maintain Partner function LS in output type
Maintain partner role "LS" in WE20 which i have not maintained.
Creation of condition record with Dispatch time - Send immediately
Now i am able to trigger IDOC when Delivery is created. Thank you for help.

Propose Custom Idoc, output type issue

Dear Experts,
I want to populate a custom idoc(Idoc already existing) by proposing the output type in the purchase order for which I created a output type and made an entry in Application 'EF' (NACE),
Also created a process code thru we41 and assigned both of these in the outbound parameters of the partner profile.
But for some reason I'm getting an error while propsing and saving the purchase order, Is there a way that I can identify why the error occurred.
Or can some one shed some light if I need to do any extra configuration if I'm playing with a custom Idoc.
Thanks for all
-Amit

>
Vinod Kumar wrote:
> Have you done the partner profile configuration in WE20. Have you mentioned message control? What is the exact error which is appearing while saving PO?
>
> Regards
> Vinod
Vinod,
I did all the partner profile configurationand maintanied message control too, While saving I'm not getting any error, but after saving, if I go back to the output type and see the output is in Red coulor (Indicating failure), I'm not sure how to check where the error occured.
Thanks
-Amit.

FM not getting read in Idoc ?

Hello All,
In WE20 --> Partner Type KU --> kunnr --> Outbound Parameters -->
Partner function and Message Type --> Message Control --> Process Code --> Function MOdule (IDOC_OUTPUT_DESADV01).
I found a user-exit in this and want to check whether the program stops at this User-exit or not.
So when I keep a break-point in this FM : (IDOC_OUTPUT_DESADV01) it's not stopping but the Idoc is generated.
I went to Tcode VL02N --> Extras --> Delivery Output --> Header --> Selected an already existing record --> Repeat OUtput Button --> save.
The Break-point is not getting stopped at the FM : (IDOC_OUTPUT_DESADV01).
Can anyone tell me how to stop the processing when this FM is triggered ?
Regards,
Deepu.K

Hi,
Hi, your program is not stopping at user-exit because IDOCs are generated in V2 update when document is created. You can not debug it directly unles you turn the "update debuggin" on
Follow these steps.
- Go to VL02N.
- Select Extras --> Delivery Output --> Header --> Selected an already existing record --> Repeat OUtput Button.
- Now here, before saving active debugger using command '/h'. Now save the document
- As you have turn the debug on, it will start debugger.
- In debugger go to the tab "setting".
- Here you select the checkbod "Update debugging" and hit save on top.
- Now press F8. It will open one more session for you to debug in update.
- Now in this session you select breakpoints from menu> breakpoint at> function module--> give fm IDOC_OUTPUT_DESADV01.
- Now when you press F8, it will stop in the FM.
- Similarly if you know the function module name of your user-exit "EXIT_XXXXXXX_YYY", you can can put a break-point at that also with
menu> breakpoint at> function module--> give fm EXIT_XXXXXXX_YYY. This will stop the debugger in your exit. ( this also you do in update debuggin in the extra session which opens).
Let me know if you have any question.
Regards,
RS

IDoc output is not showing blank fields before the carriage return

When we produce the Material Master IDoc (MATMAS), we send it to a ascii file, to a file port. That works fine when we execute BD10 to produce the IDoc and the file. But, the 3rd party mapping software wants to see every field, even if blank, in each segment it is fed. So, let's say the E1MARCM segment is 750 chars, when you add up all the field lengths in the structure, but the last 5 fields are blank. SAP does not include those trailing blanks at the end of the segment in the file. It just puts a carriage return. How can we configure it to output the trailing blanks?

Hi Mark Mathison
In IDoc ....if no value is passed in to that field then, the field wonu2019t be populated in Doc....
There is no chance of getting blank field in IDocs...
Ramesh

IDoc output type not getting configured in IDoc-File scenario

Similar Messages

Maybe you are looking for