Problem during transporting output type

HI All,
I transported the output type to production with some changes. But in Production whole output type got deleted? how can this happen?
Saurabh

thx

Similar Messages

Problem during transport

Dear All,
Now i meet a problem during transport my ABAP in dev to prod server. Not sure is BASIS or my problem.
The error is "Request after end mark"
One more question is for the transaction code STMS, the status for production server should be LOCK or IMPORT QUEUE IS OPEN? If it should be IMPORT QUEUE IS OPEN, how i going to do it cos now our status is LOCK?
Thanks for ur help....
regards;
jee

Hi,
The "Request after end mark" will be displayed due to the following:
Requests after the end mark are not imported during the next import. The end mark is automatically deleted only when the next import has completely ended. Afterwards, the requests can be imported. You can see the legend information in the following website:
http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a3847acc11d1899e0000e829fbbd/content.htm
However, as per your questions I understand that the TMS configuration is not proper. Can you check the r3trans and the transport routes/layers again and see what is missing?

Problem with the Output Type and Transaction ME9F

Hi,
      I have an Output Type (xyz) and Program (abc).
      If for ME21N i give the output type ( xyz ) the n am able to get the Spool and
      Printout.
      If for ME9F i give the output type ( pqr) then am able to get the Spool and
      Printout.
      Problem is :---
      when am using O/P Type ( xyz ) for ME9F then am abel to process but am
      not able to get the spool and not even printout.
      I want to know where it can be wrong.
      It's a high priority object.
Kindly help me out.
Thanks,
Zia.

hi Zakir,
1.check the output type under
apllications 'EF' IN transaction NACE.
2.select that ef and press the push button output types .
3. now check ur output for is present here or not ..
just click the position button and give ur output type ..
4. when u find ur output type .. select that o/p type and click processing routined on the left side where u will see ..
when u do this
u ll see the details like
output type . the output type "
application . 'EF'
and the mode of medium .
1. print out
2. fax .
6. edi etc.
this is the way to check what are the mediums present for the output type ..
check whether u r <b>entries (xyz) and (pqr) are having medium 1.</b>
if its missing then assign it ..
regards,
VIjay

IDOC Posting problem Through Billing Output Type

Dear Friends,
I have strange problem for IDOC posting through Billing Output Type.
We are using same output type for Partial / Final settlements through Billing Output type.
For Final settlements IDOC posted and generated account document is perfect, But for Partial settlement we are always getting message data is missing "No batch input data for screen SAPMF05A 0700 (Message no. 00 344)".
I tried to reprocess same IDOC in foreground then we are getting message "Posting is only possible with a zero balance; correct document"
(Message no. F5 060).
Could you please suggest me
Thanx in Advance.

solved

Problem in creating output type

Hi,
i want to create a separate output type for purchase order printing . I have written one driver program in development client which calls the smart form upon execution . Now i want to attach this driver program with a output type and that output type will be attached with purchase order creation . I am using tcode NACE in the config client . When i am tring to attach the driver program with the output type system giving error saying driver program does not exist since it was created in other client . Then i used tcode scc1 to copy the program from development client to config client but the problem remains same . Can anyone he

Please find the error message.
Entry ZMMDRIVER_PO_RETURN does not exist in TRDIR (check entry)
Message no. 00058
Diagnosis
Input values must be defined in Table TRDIR. The value or values 'ZMMDRIVER_PO_RETURN ' are not specified in this table.
Procedure
Check whether the input is correct and correct if necessary.
Procedure for System Administration
If this is not an incorrect entry, check the system settings and change them if necessary.
If there is a connection to the Customizing system, you can maintain the system settings by choosing Customizing in the Performance Assistant or Maintain Entries (F5) when displaying the help in a modal dialog box.

Problem in using output type for purchase order

Hi experts,
I am using output type for first time so may be i have done wrong configuration for po output type.The steps i have done are :-
1) Going to tcode NACE->Selected the row u201CEF Purchase Orderu201D and clicked on u201CProcedures".
2) In procedures there are 2 procedures for the application EF (Purchase Order). To proceed further, we would need to find out the procedure that is currently active.Gone to transaction SPRO. In this, navigate as Materials management -> Purchasing ->Messages -> Output control -> Message Determination Schemas ->Define Message Schema for Purchase Order
3) Clicking on u201CAssign Schema to Purchase Orderu201D. So, the procedure RMBEF1 is active for EF (Purchase Order) .
4) Go back to transaction NACE. Select u2018EFu2019 and click on u201COutput typesu201D.
5) Let us use the output type u201CNEU name purchase orderu201D for this purpose. Double-click on NEU.
6) Ensured that the checkboxes u201CAccess to conditionsu201D and u201Cmultiple issuingu201D are checked and the access sequence is 0001(DocType/PurchOrg/Vendor).Only 0001 and 0002 is available in f4 help for this.
7) Now clicked on u201CProcessing Routinesu201D on the left hand side. Ensured that there is an entry for Medium u2018Au2019 (Distribution ALE).
8) After that going back to the main screen of NACE. Select EF (Purchase Order) and clicked on u201CCondition Recordsu201D.
Select NEU and clicked on u201CCondition recordsu201D. The pop-up box appears that gives three radio button option :-
1) Purchasing output determination :purchasing org / vendor for EDI
2) Purchasing output determination :doc. type / purchasing org /vendor
3) Purchasing output determination :document type
but it is not having option only for purchasing organisation through which we can send idoc for changes or creation of PO in that particular pur.org now if i choose 2) i have to give doc type and purchasing org both bcoz they are mandatory fields and value for vendor.
9) Also i have done the necessary ALE configuration (not covered in this document). In the partner profiles, use the message type u201CORDERSu201D and the IDOC type u201CORDERS05u201D.In the tab u201CMessage Controlu201D, used the process codes u201CME10u201D and u201CME11u201D for u201CPO Createu201D and u201CPO Changeu201D respectively.
but the idoc is not generated many times when po is changed and when once it is generated it is giving error
Please suggest solution.
Thanks in advance
nehavt

In me22n in messages tab after looking into processing log it is giving->No recipient found for message type ORDCHG in the
ALE model ,next time giving error as no idoc items belonging to purchasing document found,when i changed message type to ORDCHG the status is green in messages tab it is giving-> error occured while idoc xyz is sent and in WE02 status is red 02
error passing data to port(could not find code page for receiving system)

Problem during transport of transaction variant.

Hi Experts,
Can any one tell me, the creation of transaction variant is client specific or not????
As because a new transaction variant created through transaction code 'SHD0' is not getting transported properly from one client to another client.
Kindly suggest a solution.
Thanks & regards,
Rupam.

Hi,
You can make it client specific as well as transportable.
When saving your transaction variant in SHD0, if you select Package as "$TMP" or press Local Object button, your variant is client specific.
If you want to transport it to another client, get the relevant package number from your Technical person or BASIS person, Then enter that package when saving. You'll get a transport Request number after giving the relevant Package.
Then you can transport without any issue
Creating transaction Code for that variant
When you are back on the Transaction Variant (SHD0) screen, press Shift+F6 or click the goto
menu and press the create variant transaction button.
Through this transaction SE93 will be executed. Enter the transaction name you want to create
and any other required field and now press the save button.
Tick u2013 Cross Client.
EG:
Transaction Code u2013 Z Transaction code that going to use in future
Transaction u2013 Standard Transaction code
Transaction Variant u2013 Variant that created.
At the point of saving get the transport request.
Best regards,
Anupa

Problems when transporting from DEV to PROD

Hi experts, I have problem during transport from DEV to Production.
We have a DEV, QAS and PRODUCTION and we have transport from DEV to QAS very well. But when we transport from DEV to PROD, recibe an error like:
After beginning the import method RS_IOBC_AFTER_IMPORT for Objects types IOBC mode (activation)
Failed to verify catalog InfoObjetos ZCM_UNIMET_CHA01
The InfoObjeto ZCM_RENC version does not exist in active
The InfoObjeto ZCM_RENM version does not exist in active
1.The Query is: Wy if the transport go OK from DE to QAS, then The transport from DEV to PROD terminated in error?.
2. There are any items to check in production before to transport?.
PD: All of the Objects in DEV are in ACTIVE status
Tanks,
Ramon Sulvaran

The transport ended in QAS with error code (4) and ended in Producion with error code (8), the detal of the error in Production begin with:
Home After import RS_ODSO_AFTER_IMPORT method for type (s) ODSO object (trigger mode)
Activation of DataStore objects of type Object
Check DataStore objects of type Object
DataStore Object Verification ZCM_DS01
The DataStore object is consistent ZCM_DS01
Burning the DataStore objects of type Object
Internal activation (DataStore Object)
Pretreatment / Creating DDIC objects to DataStore Object ZCM_DS01
Table / View / BIC/AZCM_DS0100 (type 0) DataStore object recorded ZCM_DS01
Create / Delete the indexes for the active table
Table / View / BIC/AZCM_DS0140 (type 4) recorded ZCM_DS01 DataStore object
Type of table / BIC/WAZCM_DS0100 recorded
Table / View / BIC/VZCM_DS012 (type VIEW) recorded ZCM_DS01 DataStore object
Log ZCM_DS01 DataStore object changes was recorded successfully
Writing Object Catalog entries (Tadiran)
He has written the object TABL / BIC/AZCM_DS0100 in catálgo objects (Tadiran)
He has written the object TABL / BIC/AZCM_DS0140 in catálgo objects (Tadiran)
He has written the object TABL / BIC/VZCM_DS012 in catálgo objects (Tadiran)
He has written the object TTYP / BIC/WAZCM_DS0100 in catálgo objects (Tadiran)
Activate all ABAP Dictionary objects (5):
Error / Warning in progr.activación Dict., Detailed log> Detail
Activate table / BIC/AZCM_DS0100.
Lack of expansion to the category table
Lack of extension category for include or subtype .......
When i go to BW Production to check teh object. I see tha the Object was create but in inactive status (grey color). When y Try to Actiavate it y see the error: Error/ Warning in program Activation Dcit. Detailed Log -> Detail

Output type for Proforma Invoice for return delivery from delivery type RLN

Client require Output type Proforma Invoice for return delivery to vendor. As such return item category is not relevant for pricing so from delivery to proforma invoice can not have with p-ricing. I got quantity correct but pricing is coming Zero.
Client have ZPAC as packing list output type from delivery which shows quantity and pricing. So decided to use the same logic to pull pricing for proforma invoice from delivery.
Here delivery has standard output ZPAC as packing list with access sequence Z002 as Delivery Type.
I want to pop up output type for all return delivery so using access sequence with delivery type/vendor.
Vendor filed does not exist in delivery output type so brought that firld LIFNR.
It is assigned to procedure and maintained ZPRO output type for Proforma invoice. Asigned VV21 on front end.
Problem Still automatic output type ZPRO is not poping up. What type of access sequence will help me to pop up or what in configuration am I miising?
Appreciate help for solution at earliest.

Hi Padamsree,
I know Pricing & output very well. I need profomra invoice to be printed with quantity & value for return goods to the vendor. Pricing is associated with Item category RLLN for delivery type RLL which is return type delivery.
I need to have pricing in my Proforma invoice which is copied from delivery to billing document VTFL. Just check well how it is working in the system & if you know please answer so that it should be workable on the system. As theoretical answer may not be helpful. Appreciate for your time.
Thanks

Output type for ORDCHG is not created in PO

Hi,
We have a problem for the output type autogeneration when a PO is changed (ORDCHG).
The scenario is the next:
- We have a Z output type for the creation of the PO. It works fine (the outputy type is generted and the idoc sent)
- We have another Z output type (ZCG3) for th PO change. The output type is not generated automatically whe you change the quantity for example. The strange thing is that if you create the output type manually and you send the idoc and later you change again the PO, now the output type is generated automatically. So it is like it is necessary a previous output type ZCG3.
Do you know where could be the problem?
We have the condition records as the other output type. Also we have marked Multiple issuing and in WE20 we have 2 entries for message ORDCHG in message control (one entry with change message flag marked and the other one without to mark).
Thank you in advance,
Manel

check the "MULTIPLE ISSUING" option in NACE.
NACE -> Select Application EF -> Click on Output types -> Select output type -> Click on Details Button -> Go to General Tab -> Select Multiple Issuing option
Regards
Vinod
Edited by: Vinod Kumar on May 3, 2010 4:43 PM

OUTPUT type document archiving is failing

Hi,
We are generating the OUTPUT type documents for billing invoices. For one of the output type the documents are not storing to content server.
tRFC request is generating but it is failing with the below error
SAP ArchiveLink: Obj. type not assigned to storage syst.(Customizing)
I have checked the configuration settings. NACE,OAC0,OAC3,V/33 etc... Everything looks fine
Documents were generating and storing to Filenet for other Output types. Only having the problem with one output type.
Regards,
Sudheer T

Hi Santosh,
It is already maintained. with Print and Archive
Output staus is showing as green, but the document is not storing to Filenet. Even not able to see in attachment list.
tRFC is failing as below
find the root cause as the TOA_DARA details are not updating for AR_OBJECT and SAP_OBJECT fields.
But not sure whether these details upload from the SAP Form or from report.
Regards,
Sudheer T

Help viewing an output type requirement

We have a few custom output type requirements and I need to know how to view them. When I go to the "Control Data" overview (through SPRO) and click the dropdown for the output requirement the custom requirements do not show up. We are having a problem with an output type calling the wrong print program and we believe that it has to do with the requirement associated with that output type.
Regards,
Davis

Hi Davis,
Please try transaction NACE and VOFM to see the output type configuration and requirement.
Regards,
Ferry Lianto

Output type mot triggered

Hi,
The process is that
A sales orders are getting created with the batch job once the sales order has been generate a Output type is triggers
and mail sents to customer about the order confirmation.
The medium os output type is "Send external" and dispatch type is "3 - Send with application own transaction"
Our problem is this output type has not getting triggered it in Yellow only.
if we change the dispatch time form 3 to 4 - Send immidetiatly then its working fine.
why this is happening?
how to resolve this so that there will be smooth operation with dispatch time as 3?
regards,
anup

See, you can process a message immediately by updating the application document or you can process it at a later time. For later processing you must use the report program RSNAST00 or a corresponding application function.
Thus there are some individual possibilities are:
Time 1: The message is processed through report program RSNAST00. This report program can be scheduled periodically or started manually.
Time 2: As in time 1, but the message contains an earliest processing date and a requested processing time. The message is ignored by report program RSNAST00 before the requested date.
Time 3: The message is selected and processed by application specific programs. Processing can take place online or in the background.
Time 4: The message is processed when the application document is saved. No further processing of the message is necessary.
So, check your communication method & transmission medium for dispatch time 3 for your requirement : A sales orders are getting created with the batch job once the sales order has been generate a Output type is triggers and mail sents to customer about the order confirmation. Check the output condition record maintained.
Also you can use user exit MV45AFZZ for automatic generation of email.
Hope this can assist you.
Thanks & Regards
JP

PO Output Type / Processing Routine Problem

Hello everyone,
I cannot seem to find any reference to the problem described below.
I have encountered a problem by migrating from SAPFM06P to SAPLMEDRUCK during an ECC 5.0 upgrade, at a client where I am under contract as an ABAP Developer.
Here is some background to the situation. The client is currently migrating from version 4.6C to 5.0 and thought it was a good idea to upgrade their purchase order messaging programs from the outdated SAPFM06P, which was utilized in version 3.x, to the newer program SAPLMEDRUCK implemented for use in version 4.6.
Specifically, Message Output (ME9F) controls the output of purchase order messages in foreground, when the purchase order message is saved and the "further Data option" of the PO message contains "requested processing" equal to the value of "send with application own transaction". This way, the actual messaging can be controlled in foreground and "breakpoints" can be set to display tables and fields. Behind the scenes, the message status program RSNAST00 is executed by ME9F program RM06ENDR_ALV. During this execution, it locates the message (NAST) record from the purchase order and the (TNAPR) configuration, which links the output type to the ABAP print program and SAPscript layout set. The specific problem is: in RSNAST00, the external call perform "PERFORM (TNAPR-RONAM) in PROGRAM (TNAPR-PGNAM) USING RETURNCODE US_SCREEN IF FOUND" does not pass NAST information to the called program (TNAPR-PGNAM). I know no NAST table information is passed because I set a break-point on the perform and single step to the print program. Therefore, the purchase order is unknown by the print program (TNAPR-PGNAM) and results in an error and no purchase order print is provided. Needless to say, this was tested with a new "Z" version of SAPLMEDRUCK. So, I changed the program name (output type processing routine) in configuration to SAPLMEDRUCK, but there again the NAST information is not passed to the print program from RSNAST00. Ironically, I reverted back to the older "z" version of SAPFM06P and NAST and TNAPR information is passed to the print program thru the external call perform quoted above. I prefer to not modify the SAP original code for RSNAST00, which is used in many other applications.
One other note, I had previously performed this maneuver on one different occasion with very successful results.
Has anyone ever encountered this problem in a 5.0 environment (running Windows NT and MSSQL and SAP BASIS 6.4).
I know this is long winded, but I wanted to explain the background of the entire situation.
Any and all help would be appreciated. Thanks in advance,

Dave,
Your entry points (like form ENTRY_NEU) should remain in your current version of SAPFM06P. Change that form to reflect the function calls in the new SAPLMEDRUCK form (ENTRY_NEU) (calls to ME_READ_PO_FOR_PRINTING and ME_PO_PRINT.
Look at the example below:
Here is the form in your old (Z) version of SAPFM06P:
FORM ENTRY_NEU USING ENT_RETCO ENT_SCREEN.
XSCREEN = ENT_SCREEN.
IF NAST-AENDE EQ SPACE.
   XDRUVO = '1'.
ELSE.
   XDRUVO = '2'.
ENDIF.
CLEAR: XFZ, XOFFEN, XLMAHN, XLPET.
*- Anstoß Verarbeitung -
CLEAR ENT_RETCO.
PERFORM LESEN USING NAST.
MOVE RETCO TO ENT_RETCO.
ENDFORM.
Here is form entry_neu in your new (Z) version of SAPFM06P:
INCLUDE FM06PE02                                                   *
form entry_neu using ent_retco ent_screen.
data: l_druvo like t166k-druvo,
        l_nast like nast,
        l_from_memory,
        l_doc   type meein_purchase_doc_print.
clear ent_retco.
if nast-aende eq space.
    l_druvo = '1'.
else.
    l_druvo = '2'.
endif.
call function 'ME_READ_PO_FOR_PRINTING'
       exporting
            ix_nast        = nast
            ix_screen      = ent_screen
       importing
            ex_retco       = ent_retco
            ex_nast        = l_nast
            doc            = l_doc
       changing
            cx_druvo       = l_druvo
            cx_from_memory = l_from_memory.
check ent_retco eq 0.
call function 'ME_PRINT_PO'
       exporting
            ix_nast        = l_nast
            ix_druvo       = l_druvo
            doc            = l_doc
            ix_screen      = ent_screen
            ix_from_memory = l_from_memory
            ix_toa_dara    = toa_dara
            ix_arc_params = arc_params
            ix_fonam       = tnapr-fonam          "HW 214570
       importing
            ex_retco       = ent_retco.
endform.
Remember, the form should be in the Z version of SAPFM06P - not the Z version of SAPLMEDRUCK. Make sure the configuration (TNAPR) has the SAPFM06P program name and entry point.
It should work. Let me know how it goes.
Rick

HELP Regarding Problem Found during transportation

Hi Experts
I was transported my request from DEV to PROD
When i am Importing my Objects in Producton server System is throwing
this Error.
--Start of the after-import method for object type R3TR UPDR (Activation Mode)
Info object VV00B is not available in version A
ERROR R7 245 when handling objects with type R3TR UPDR .
--Start of the after-import method for object type R3TR IOBC (Activation Mode)
InfoObject VV00B is not available in active version.
InfoObject VV175 is not available in active version
InfoObject VV176 is not available in active version
--Start of the after-import method for object type R3TR ISCS (Activation Mode)
InfoObject <No Text Available in this Language> ( VV00B ) is not active, total of 3 inactive InfoObjects
--Errors occurred during post-handling RS_AFTER_IMPORT for CUBE L
Ended with return code: ===> 12 <===
I am in a very confusing state
THIS IS THE FIRST TIME I AM FACING THIS TYPE OF PROBLEM
its very urget
<b>Any thing and Every thing will Rewarded</b>

Hi Raj,
check this OSS note 1033750
Symptom
When you collect Content with transaction RSOR the system issues error message R7 245: 'InfoObject &1 is not available in version A'.
Other terms
R7 245
Reason and Prerequisites
This problem is caused by a program error.
Solution
SAP NetWeaver 2004s BI
Import Support Package 13 for SAP NetWeaver 2004s BI (BI Patch 13 or SAPKW70013) into your BI system. The Support Package is available once Note 991093 "SAPBINews BI 7.0 Support Package 13", which describes this Support Package in more detail, has been released for customers.
In urgent cases, you can implement the correction instructions as an advance correction.
You must first read Note 875986, which provides information about transaction SNOTE.
To provide information in advance, the notes mentioned above may already be available before the Support Package is released. In this case, the short text of the note still contains the words "Preliminary version".
Before you implement an advance correction (if one exists and you want to implement it), see Note 875986. This collective note contains all corrections that refer to the SAP Note Assistant and prevent problems during the implementation. You must call transaction SNOTE again after you have implemented the collective note.
Hope this helps,
Sudhakar.

Problem during transporting output type

Similar Messages

Maybe you are looking for