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

Similar Messages

Output type not triggered during Delivery Order - pls help

Hi,
Need some help.
I'm trying to setup output determination for delivery. It's a new output type for delivery.
There are some checking that I want to build in to determine whether the output type is to be generated. Therefore I have to make sure of requirement (routine). However, after putting in the configuration, coding the requirement and creating the condition record, the output type still cannot be generated. When I go to VL02N to check the Output Determination Analysis it says the requirement " " is not fulfilled. It's not even calling out the requirement number that I assigned in the access sequence.
Any idea what could be wrong?
This is what I've done :
1. Creating condition tables
2. Creating access sequence & assigning the condition tables to the access sequence
3. In the access sequence, assign requirement number 999. The "Exclusive" indicator is not ticked.
4. Ensure that the requirement 999 is activated in tcode VOFM.
5. Create output type, assign the access sequence to the condition type.
6. Assign the condition type to the output determination procedure. Make sure the "Manual" checkbox is not ticked.
7. Assign the delivery type to the output determination procedure.
8. Create condition record.
Note : when i created the condition record, I am not able to assign a Partner Function (for eg. SH) to the record. However in the config for the output type I've already configured for that Partner Function "SH" to be allowed for that output type.
Appreciate suggestions & feedback.
Thanks
Rgds,
L

Hi,
When I go to VL02N to check the Output Determination Analysis it says the requirement " " is not fulfilled. It's not even calling out the requirement number that I assigned in the access sequence.
This is because in requirement you put certain conditions should be fulfill then out put should trigered,
Example - if you maintained condition in requirement that user must maintain loading point
Now when creating delivery user not maintained loading point then output will not trigered, so user must maintain that then only it will trigered output.
Same problem just now solved, check which data maintenance conditions in routine and try to maintain that.
Kapil

WMTA output type not determining in outbound delivery

Hi,
Im in is-retail we are using lean WM for automatic transfer order creation, recently we made immediate delivery also, after this auto TO is not creating and WMTA output type also not determining in delivery.
pls help me any body why out put type is not determining and what is the solution?
Regards,
MMReddy.

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

Process type not determined during ISU - CRM Contract replication

Hello Experts,
Process type is not getting determined during the ISU -> CRM contract replication.I could see that all configs are in place.
Please could you suggest what could have impacted this.
Regards,
Ravi

Hi, Nikhil
Do you read this document?
service.sap.com
/utilities
SAP for Utilities - Product Information
Cookbooks&Guidelines
IS-U/CRM Contract Integration
Denis.

Output type not determined in Sales Order

Hello Friends,
I am facing a problem.
I have maintained the O/P condition record for O/P type for order confirmation.
While creating sales order, in the determination analysis for O/P , it shows as O/P found, but the same is not added in the sales Order outputs.
Can somebody advise me what is missing ?
Regards

Harsh Mathur ,
1. You need to maintain Condition records in VV11 for BA00 (Key combination - order type)
2. If already created Check whether the records are existing through VV12
3. If yes, then enter into your sales order in VA02 Mode
4. Check Extras --> Output --> Header --> Edit
If status is yellow or green then it is ok. Output = BA00, Medium = Print output, Function = SP
Then Choose the line and click "Communication Method" Enter Logical destination - LP01 and activate the indicator against "Print Immediately"
Click Back button --> Click "Further Data"
Under "Requested Processing" header
Dispatch time = Choose the option accordingly
save it.
Then counter check the config by running sales transaction without saving check
Check Extras --> Output --> Header --> Print Preview
if the output is shown then you have succeded
Regards
Sathya

Send output as PDF during background job

Dear
can you suggest how to send output of schedule job log in PDF as attachment insted of HTML.
If i schedule any job & set spool receiption, then spool log is sent as html attachment,
but i want to send it as pdf is there is any way to change defalult attachment type.
In addition to it can i set message text during scheduling job, or can i insert message text in body along with
attachment. So that i can type desired message in Body, any standard template is available to change its text.
regards
Pranav

Answer on the first question:
trxn SCOT
double click the INT node that sends your mail out
suported adres typs: internet click on SET
There you have 3 report types: set these to PDF. ( you can not set BO/Link to pdf)
I have to admit i have never tested, so let us know if this works !
Answer on the second question:
Not really ( AFAIK) , you can modify the header line of the message (and spool) via:
SM36 , shedule the job, during every step you can click at the bottem on "print specifications", then properties
There you can modify Name and title.
Maybe a cover page could fit your needs partially?
http://help.sap.com/saphelp_nw70/helpdata/en/d9/4a951b51ea11d189570000e829fbbd/frameset.htm

Getting error "Codepage could not be determined" in background job

<i>Hello Friends,
I am running a background job with a variant and the job get cancelled with the following error message.
Codepage could not be determined
Message no. FES025
Please give your valuable comments.
Thanks,
Senthil</i>

Hi,
Check the oss note 765763(Setting the upload/download codepage for a SAPGUI connection) released for this purpose, as per the documentation of this note, you need to modify the standard program LSFESF03 in order to get rid of this error,
Also check the note 882961(File download: codepage conversion error FES024)
Hope this helps,
Rgds,

Output Type not automatically determined at invoice creation

Hi Friends,
I am facing a problem that while i am generating the invoice for a particular billing document type, the output type is not automatically being determined. Instead, I have to go into the invoice in change mode (VF02) Header>Output and assign the output type to it and select the local printer and save in order to print the invoice.
I am generating the invoice for this Invoice Type/Output type for the first time.
Please suggest the possible causes.
Regards,
Pankaj

Hello Pankaj,
Suppose you are using output type RD00 for invoice print out. You have maintained the condition record for RD00 in transaction code VV31. The most important thing here is the assignment of the printer.
Suppose for output type RD00 you are maintaining the condition record for key combination - Sales Organization + Distribution Channel + Division.
At the header level you will see the Sales Organization & Distribution Channel & at the item level you will see the Division.
Sales Organization = BP01
Distribution Channel = 01
Division.............Name..........Funct.........Partner............Medium......Disp. Time.....Langu
01............... Std Division..........BP............--......................1......................3................---
Select the line item & click on Communication. Here assign the output type which you will use for the print out. Now Save the condition record.
After doing this try running one sales cycle - sales order - delivery - invoice. Save the invoice & now check in the change mode (transaction code VF02) the system will determine the output type RD00 automatically.
Note:
1. In the create mode the system will not display the output type RD00, after you have saved the invoice the output type will be determined automatically.
2. Also check if there is any requirement assigned for the key combination in the access sequence (IMG - Sales and Distribution - Basic Functions - Output Control - Output Determination - Output Determination Using the Condition Technique - Maintain Output Determination for Billing Documents - Maintain Access Sequences)
With best regards,
Allabaqsh.
(Idhasoft Ltd.)

MM - output type not *allways* assigned during posting with MB1C?

Hi guys,
in one of our R/3 4.6C systems we have developed an automation process, where one of the steps is to call transaction MB1C in background mode and to do some postings in K-stock (expenditure), depending on input data. There are few output types, which are supposed to be attached automaticaly to the newly produced MM document, and further to be printed out by end-users.
Everything goes as expected at development and test stage. Even in production there were allmost allways no problems. But in some unpredicted occations output types are not automaticaly assigned. In case output types are not automaticaly assigned, end user is supposed to assign them manualy, which is annoying (obviously).
The problem does not arise at our testing system.
Due to roll-out of the automation process to more stores at the client' company this problem rises more times.
We have started some investigation, but are stuck up to now.
Does anyone have a clue what might goes wrong and where to push our efforts in order to resolve the problem?
Many thanks in advance.
Regards,
Ivaylo Mutafchiev
SAP consultant
<removed by moderator>
Edited by: Thomas Zloch on Jan 13, 2012

Hi,
thanks for comment. Perhaps I missed something in my explanation. There are few output types, which are assigned automaticaly to MM-document when it is posted. "Few" means 8. And all of them are assigned as expected in case of manual processing, and even when posted in this automation procecess in background.
Well, I have found the problem. As I explained, this is an automated process. There might be more than 1 document to be created one after another. Allways the 1st document is created correctly with output types assigned, but all next documents (2nd, 3th...) are created without output types assigned automaticaly.
The issues was - there was missing check in the recording RM07M-XNAPR = 'X' (GI/GR slip Print = 'X'), and further output types were not assigned for the 2-nd (and next) documents. Strangely it appears in the document preview (via MB03 for example), even if it was not supplied. Even more strangely, 1-st document gots all the output types assigned, which perhaps was due to some inheriting behaviour.
We reproduced the problem in test system and fixed it.
Thanks again.
Regards,
Ivaylo

Output type not automatically determined (no output device specified)

the output device is already specified for this output
we dont want to manually add the output on all the invoices where the output was not automatically determined before... what should we do?
is there a way not to manually add them?
thanks in advance
Pablito

Hi
You really dont need to add the output in all these documents.
You have to maintain the masterdata for output records in VV31.
Now just open all the invoice documents one by one in Change mode through transaction code VF02 and just save it
Whenever a document is opened in change mode, the output gets automatically triggered. Hence the output type will be automatically populated in the output screen. Once you save the document, the output gets successfully executed, and you will get the desired document
Reward if this helps you

Spool not generated in BAckground Job

Hi,
I am trying to schedule RSNAST00 in a background job. My problem is that when the job gets finished i cannot see a spool for the output, any pointers to this issue will be appreciated.
Regards,
Sharadendu

Go to transaction SM37 and check job log.
It is possible that something is going wrong in your program. I would suggest you to debugg background job.
To debugg just select job in SM37 and in command window(Where we type T codes) type JDBG and press enter. This will open debugger. Press F7 for approx 4-5 times. Now your program will be opened in debugg and you check why spool is not generated.
let me know ig this helps.
Regards,
Jigar Thakkar.

Output type not triggered on time

Dear All,
I have an issue on output determination.
We have a list of outputs on Delivery which will be determined after the loading start checked in Shipment based on activity profile assigned to the Shipment type.
Out of all the outputs, only one output is not printed on time (But it is determined on time).
We checked the condition record and everything, all found ok. But still we are facing this issue.
Could anyone suggest me on this.
Regards,
Mullairaja

Hi Mullairaj,
If i understand it right, you are able to trigger output for both the cases but only one is picked by batch job and so you are only seeing one "Green" output but the other stays "Yellow". if this is right then did you check if the batch job is calling program RSNAST00 with right variants ?. Does this JOB has variant to pick both the Outputs.
Let me know.
Thanks!

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

Output type not proposed in Message Control when PO is created

Hi,
DETAILS
I have set up the system to send a IDOC when a PO is created. I have done the following settings in the system to send the IDOC using the message control functionality in the PO creation screen.
1). Created a new output type ZNEU which is an exact copy of NEU output type provided by the SAP system.
2). Assigned the new output type to the output determination procedure.
3). Enabled the new output type ZNEU for ALE distribution.
4). Maintained the condition records in the system for the output type ZNEU such that for the P org, endor and Docmuent type combination the output shall be proposed.
5). Maintained a partner profile( Logical System ) and assigned the output type ZNEU to this partner profile.
6). Created a Distribution model for Sender ~ Receiver for ORDERS message type.
PROBLEM
When i create a PO the new output type is not getting proposed by the system. I am not sure why it is not getting porposed in the message control.
I tried to manually enter the ZNEU output type in the system to see if the system is accepting. I am getting an error
Partner % does not exist for partner function LS
Any idea what i am missing? Am i missing any configuration or am i doing something wrong?
cheers

The output is not being proposed automatically is becuase you are missing "Condition Records" for the output type ZNEU.
Go to NACE.
Select EF - Purchase Order
Select "Condition Records"
Select ZNEU and select condition records
Now, system will bring the combinations of access sequence. Maintain appopriate record.
This will enable you to get the output type automatically in the purchase order.
Regards,
Naimesh Patel

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

Output type not determined during background Job

Similar Messages

Maybe you are looking for