Print program is not getting triggered when saving the application

Hi all,
My requirement is when i save the invoice using VF01 the print program should get triggered.
The print program is not getting triggered when saving the application even when i have configured the outtype and have attached the print program.
The setting "send immediately (when saving application)" is also checked.
I need to configure it for VF01 transaction.
The error message displayed was " please maintain output device in master data".
Regards,
Umesh

Hi Umesh
Please check if you have missed any of the following:
1. Defining Access Sequence(can use existing).
2. Defining Output Condition Type(can use existing). - Assigning the Driver Program and Form in processing routine.
3. Output Determination Procedure
4. Assign Output Procedure to Billing Types
Kind Regards
Eswar

Similar Messages

"Message Processor" does not get assigned when saving the document.

Hi folks!
When creating a support message (SLFN) and saving the document usually the BP of the current user got assigned to the partner funtion "message processor".
This used to work but does not anymore. Now I cannot find the reason why.
I think I could achieve this via customizing "Make Settings for Change Transaction Types" and using "Specify Copy of Current User" but I am pretty sure this was not customized before.
I could use partner determination procedure, too. Access sequence "User" but still I am not sure this was customized before.
I am using SLFN transaction type service provider scenario (SLFC0001)
Anyone got an idea?
Thanks in advance.
Regards
Edited by: Christian Kaunzner on Mar 25, 2009 5:15 PM

Hi Christian,
did you solve this issue on your own? can you share your experience?
thanks
Pedro Rodrigues

Driver program is not getting triggered

Hi Experts ,
I have assigned driver program and form under the application ME to the output type WE01 and WE02 and WE03 .But my program is not getting triggered.
How to check whether the Form entry is getting or not ?
i have also tried putting the break point in the program.
Please suggest .
Thanks

Hi Kartik,
Thanks a lot !
Update for you ......
By refereing std prog i have written the form routine like below.
FORM entry USING ent_retco ent_screen.
xscreen = ent_screen.
CLEAR ent_retco.
PERFORM check_input USING nast-objky.
ent_retco = retco.
    perform fetch_data.
    perform print_control.
ENDFORM.
form check_input using objky.
nast_key = objky.
select single werks from t001w into t001w-werks where werks = NAST_KEY-p_werks.
if sy-subrc ne 0.
   message 'ENTER VALID PLANT' type 'E'.
endif.
endform.                    "check_input
But i am not able to debug the code...
Break point is not triggering the code.

In VA02 transaction which exit is triggering when saving the data

hi all sap gurus,
In VA02 transaction which exit is triggering when saving the data

Hi Reddy,
The user exit and badi tried for this transactions are
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
V46H0001 SD Customer functions for resource-related billing
V45W0001 SD Service Management: Forward Contract Data to Item
V45S0004 Effectivity type in sales order
V45S0003 MRP-relevance for incomplete configuration
V45S0001 Update sales document from configuration
V45P0001 SD customer function for cross-company code sales
V45L0001 SD component supplier processing (customer enhancements)
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45E0001 Update the purchase order from the sales order
V45A0004 Copy packing proposal
V45A0003 Collector for customer function modulpool MV45A
V45A0002 Predefine sold-to party in sales document
V45A0001 Determine alternative materials for product selection
SDTRM001 Reschedule schedule lines without a new ATP check
Business Add-in
BADI_SD_SCH_GETWAGFZ Scheduling Agreement: Read WAGFZ from S073
BADI_SD_V46H0001 SD Customer functions for resource-related billing
Reward pts if found usefull :)
Regards
Sathish

Output fax not getting triggered when sales order credit block is released

Hi Experts,
I am working on an issue.
I have one sales Order which has credit block.
when we release the credit block via vkm3, then the output fax gets triggered.
I have another sales order which has credit block,
when we release the credit blcok via vkm3 , the output fax is NOT getting triggered.
If any of you has worked on this setting, request your input on where to find the settings/coding for the same.
Any advice on this please.
Regs,
SuryaD.
Edited by: SuryaD on Oct 21, 2010 9:34 PM

Hi Brad,
Thanks for your response.
Order 1: Issues output fax(ZFAX) correctly when block is released.(i see output zfax in te output screen)
Order 2: Fails to issue output fax(ZFAX) even when the block is released.( i dont see any output in the output screen)
I went to Go to -Determine analysis for both orders 1 and order 2.
in both the analysis i am able to see the output ZFAX.
*Analysis Output*
*Order 1                                                                    Order 2*
1. ZFAX                                                                   1.   ZFAX
    10(Z010)                                                                 10(Z010)
       0000122426                                                              0000122427
2. ZFAX                                                                   2.   ZFAX
When i click, D.Click on the output type ZFAX on both the order Analysis output screen, i see similarities.
There in just 2 differences as below.
In the above screen,
1.Order 1 ==> has some value 0000122426
2.For Order 1==> row marked 2.(in the above screen) if i D.Click on ZFAX it says
Diagnosis
Output ZFAX has already been issued. Multiple issue for this output type is forbidden in Customizing.
In the above screen
1.Order 2 ==> has some value 0000122427
2.For Order 2==> row marked 2.(in the above screen) if i D.Click on ZFAX it says
No more information is available.
Please guide as to how to initiate the debug for output processing ?
Which screen where to switch on debugger.
where to look further?
Regards,
SuryaD.
Edited by: SuryaD on Oct 22, 2010 11:41 AM

User exit not getting triggered while creating the vendor

Hi all,
I wanted to extend the idoc(crermas01) according to my reqiurement.
But when I am trying to create a vendor using the IDOC cremas01 the user exit EXIT_SAPLKD01_001 is not getting triggered.
Can anybody tell me the reason why it is happening so...........
Thanks and regards,
Vinil.

Is your Idoc generated after the execution?
Where is you break-point, it is inside EXIT_SAPLKD01_001. Please note FM EXIT_SAPLKD01_001 will not be called unless it is implemented using project (CMOD) and project is active.

Task Does not get triggered when User is created through API

Hi,
Each new user in our OIM environment is supposed to have a iPlanet account. I have configured the access policy for the same and it works.There is also a process task which needs to be triggered once the user is successfully created in the DS. Following is my issue:
1.When the new user is created through the admin console, the user is provisioned successfully to DS as well because of the access policy and the task also gets triggered successfully.
2. There is an approval workflow for another resource, at the end of which a user needs to be created through APIs in OIM. The user gets created successfully in OIM and also get provisionined to DS just like in the above use case. However, the task fails in this case. I see that the task is being triggered from the user's resource profile, but the status is rejected.
Can someone please tell me why is this happening. I initially though there was some issue with my adapter for the task, but in case 1 it works just fine.
Following is the exception I get as soon as the iPlanet connector finishes creating the user in DS:
java.lang.ClassCastException: java.lang.String
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSETFIELDSONUSERCREATE.implementation(adpSETFIELDSONUSERCREATE.java:51)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
Thanks,
Supreetha

Hi,
Have you checked the process data that you are passing to this adapter and check the mapping of process data to the adapter variable. Try to log the value which you get from process data. I got this error when I was trying to use the literal value from process data as "true" for a boolean value. This is a bug. This value is not actually a boolean value. It threw me error too sometimes back. Either you pass the boolean value from adaptor factory as a literal value or change the type boolean both in your code and the adapter.
OIM works strangely. ;) All the best,
Manila

Ps assembly processing:WBS have not be created when saving the sales order

In the ps assembly processing, I want to generate a network when I create a sales order. So I did the following steps:
1-Use the TCODE cj91 to create a standard WBS "E-000007.1".
2-Use the TCODE cn01 to create a standard network "10000000" and assign the standard WBS "E-000007.1" to it.
3-Use the TCODE cn08 to config the Network Parameters from Sales Order like below:
Material number : 600000-000000-0009
Order Type      : Z301
Std network     : 10000000
Class Type      : 020
Network Profile : Z0001
MRP Controller : 001
Std WBS element : E-000007.1
4-Use the TCODE va01 to create a sales order and add an item with the material "600000-000000-0009" and save.
    When the SAP R/3 System is saving the sales order, a WBS ought to be created u2013 based on the assignment of the standard network to the standard project.But I could not found the WBS.I thought I have do all of steps and could not found the reason.
   So I need the experts give me some useful advice and reference to resolve the problem.Thank you.
Regards
Yoda

Hi,
Maintain strategy group in material master MRP tab....
If problem still persist then check is there any credit block to that customer...if it is release it in VKM3....
Once you release it will create automatically.
Regards

Debugging the program that will get triggered for a particular output type

Hi all,
I have one program,which will get triggered when a Sales order of type 'VOR' is created.Whenever 'VOR' order is created it will trigger the 'ZALT' output type.And this output type 'ZALT'has been configured to my program.This output type configuration has been set up by my functional consultant.
My problem is I created Sales order of type 'VOR'.But I want to debug my program,which has to be triggered because of that 'VOR' sales order type,which in turn triggers 'ZALT' output type and in turn triggers my program.
My problem is I created Sales order of type 'VOR' by keeping debugging point in my program.But it is not going to my program and simply displaying sales order has been saved.
So is the outtype has been configured properly?.Do I need to go to my functional consultant?Could anyone explain in this regard?
Rgds,
Balaji

Hi Balaji,
If possible, try to repeat the output in the output type messages screen of VA02 and change its dipatch time to '1'(Through further data). Now put the break point in the program assigned to output tye 'ZALT'(You can see this in the TNAPR table) and run the program RSNAST00 through SE38. The program will stop at the break point.
If its not possible to repeat the output and if you want to check it the first time the output type is processed, ask the functional consultant to change the dispatch time in the condition record that is being retrieved for proposing the output type to '1'. Now run RSNAST00. The program will stop at the breakpoint.
Thanks,
Vinay

Urgent IDOC - EXIT_SAPLLMDE_002 not getting triggered.

I am doing an inbound idoc on message type WMMXY goods movement.
The idoc is sucessfully getting posted when tested through we19.
But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
I have activated the exit functional module, the project in CMOD is also activated.
Some one pls help me .. if u have its document pls post it to me.

Hi,
Please refer to this documentation of user-exit; may be of some help for you.
You can use this user exit to influence the processing of IDOCs of the
message type WMMBXY (goods movements) that are sent to SAP from external
systems via the MM-MOB or WM-LSR interfaces. You can also access
customer-specific processing in this case.
Call transaction and other important requirements
The user exit is performed in the function module that processes the
IDOCs of the message type WMMBXY, after the IDOC is withdrawn and
checked but before direct processing in the application has been
initiated. (That is, the data for the goods movement has already been
determined and edited, but the function module for updating this has not
yet been accessed. The standard function module for processing the
message type WMMBXY is called L_IDOC_INPUT_WMMBXY. The IDOC is processed
in an update task, which means that the source code is also executed in
the update.
If an error arises, then messages should not be issued since processing
is being carried out in the background and the result of processing must
always be returned to the ALE interface. For this reason language
elements such as MESSAGE, COMMIT WORK, LEAVE and the like should not be
used. If errors that should be passed on to the ALE interface or that
affect the result of processing are found in the user exit, you should
also use the user exit MWMIDI07(EXIT_SAPLLMDE_001) since it alone can be
used to take your errors into account (see documentation of the user
exit).
Parameters and options
The user exit in the program is the function module EXIT_SAPLLMDE_002.
In order to be able to use it, you must first create Include zxlidu10
and activate the enhancement by means of transaction CMOD. As
parameters, you can use the following data:
o   Goods movement data already determined from the received IDOC:
    -   Transaction code that is given along with the application
        function module (see interface description (import parameter
        X_TCODE).
    -   Indicator: post only if all items o.k. (import parameter X_XALLP
        ). This indicator must be set by default, to enable IDOC error
        processing.
    -   Indicator: Reset all tables (as primary call) (import parameter
        X_XALLR). This indicator is not set by default to enable the
        processing of several IDOCs. Normally you will not change these
        two indicators.
        -   Goods movement items table (table parameter T_IMSEG)
    o   Received IDOC data:
        -   IDOC control record (import parameter I_IDOC_CONTROL)
        -   IDOC data records (table parameter T_IDOC_DATA)
    This user exit can be used to:
    o   Influence the determined data for the goods movements. All data can
        be changed in this case.
    o   Analyze and process data that is transferred using customer-specific
        segments.
    o   Access additional activities.
    Examples
    A number of potential applications are described below.
A number of potential applications are described below.
o   You want to inform a user by mail when the goods movements of
     certain vendors or customers take place.
o   You want to start your own label printout, for example at goods
     receipt.
o   You want to update your own tables, for example statistical data.
o   You want to analyze a missing parts table at goods receipt and
     redirect the goods receipt correspondingly.
Reward points if helpful.
Regards,
Pankaj Sharma

IDOC - Function Exit not getting triggered

I am doing an inbound IDOC for the message type WMMBXY and using basic type WMMBID02.
This is for goods movement based on PO.
I am doing an enhancement in the includeof the function module exit EXIT_SAPLLMDE_002.
This exit is supposed to get triggered for the message type WMMBXY.
when i tested the idoc in we19 it is sucessfully getting posted. I want to check my code in EXIT_SAPLLMDE_002. I have set breakpoint and tested using we19. But this is not getting triggered. But the idoc is getting sucessfully posted but with a status message 56 An inbound partner profile could not be found( I am not sure if this has something to do with above problem).

Did you attach your exit to a CMOD project and activated the same(CMOD transaction)?
The error you see regarding the partner profiles is probably due to the non existance of a partner profile for your idoc type in we20 transaction.
Maintain the inbound partner profile in we20 transacttion.

IDOC - EXIT_SAPLLMDE_002 not getting triggered.

I am doing an inbound idoc on message type WMMXY goods movement.
The idoc is sucessfully getting posted when tested through we19.
But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
I have activated the exit functional module, the project in CMOD is also activated.
Some one pls help me .. if u have its document pls post it to me.

I am doing an inbound idoc on message type WMMXY goods movement.
The idoc is sucessfully getting posted when tested through we19.
But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
I have activated the exit functional module, the project in CMOD is also activated.
Some one pls help me .. if u have its document pls post it to me.

11g B2B Error, BPEL is not getting triggered

Hi,
We have installed 11g B2B, where we are facing few errors :-
1. We have created one protocol and multiple document definitions under it for different trading partners.
But within all these document definitions only one is working fine, for others we are facing issue. After getting successfully processed by B2B, BPEL is not getting
triggered.
Do we need to apply any patch to make it work?
2. Is there any naming convention to create protocols and document definitions?
We created protocols like "<Trading partner name>_<versionNo>_<Transaction_type>" , but we were geting agreement identification error, when we created protocol name with only version no(4010) and document definition name with transaction_type (850), that issue got resolved. We haven't encountered any issue like this in 10g B2B.
Any pointer with respect to fix this issue would be a great help. Thanks in advance.
Regards,
Saravana

Hi Saravana,
After getting successfully processed by B2B, BPEL is not getting triggered.Do you see application message getting created? Are you using B2B adapter in composite to receive transactions from B2B and if yes then which mode of integration (AQ/JMS/Fabric) are you using? Are you using Document Routing ID in Document definition?
Do we need to apply any patch to make it work?No. No patches are required.
2. Is there any naming convention to create protocols and document definitions?Yes, in case of EDI. Version should be the EDI version (for e.g - 4010) and Document Type name should be EDI document name (for e.g. 850). No restriction on Document Definition name.
Regards,
Anuj

Refresh itab is not getting triggered

hi,
SELECT ebeln
bukrs
ernam
lifnr
spras
FROM ekko INTO CORRESPONDING FIELDS OF
TABLE g_it_ekko WHERE lifnr IN r_lifnr.
DESCRIBE TABLE g_it_ekko LINES n.
grid-lines = n.
IF sy-subrc = 0.
MESSAGE s002(zsan) WITH n.
ELSE.
REFRESH g_it_ekko.
MESSAGE e000(zsan) WITH n.
ENDIF.
the message is gettig triggered first but the refresh statement is not getting triggered. i want the refresh statement should be triggered first and then the message.plz help.
thanks & regards,
santosh.

Try changing ur code like below
SELECT ebeln
bukrs
ernam
lifnr
spras
FROM ekko INTO CORRESPONDING FIELDS OF
TABLE g_it_ekko WHERE lifnr IN r_lifnr.
IF sy-subrc = 0.
DESCRIBE TABLE g_it_ekko LINES n.
grid-lines = n.
MESSAGE s002(zsan) WITH n.
ELSE.
REFRESH g_it_ekko.
DESCRIBE TABLE g_it_ekko LINES n.
grid-lines = n.
MESSAGE w000(zsan) WITH n. "warning msg
ENDIF.

Treasury workflow not getting triggered .

I have done all as given in the SAP doc ...
The release procedure for the business partner has been set up using a Business Workflow, for
which SAP has defined the standard role 20000053 'TRLOAPPROVAL' and the Workflow
template WS20000263 'WSTRLOAPPROV'.
Procedure
In order to use the release workflow for the business partner, you are also required to make
settings in Customizing for the Basic Functions area in Treasury in the following IMG activities:
By choosing u2019Activate Releaseu2019, you can activate the release for the business partner.
By choosing u2018Maintain and Activate Release Parametersu2019, you can specify the number of
release steps you require for each role category.
By choosing 'Adjust/Copy Workflow Template', make the following settings:
By choosing 'Define Standard Roleu2019, you create the responsibilities for the standard roles
delivered with the system, to which you assign users, positions, organizational units,
work centers, jobs, or people. Using the settings you make here, the system determines
the Responsible Agent [Ext.] during the workflow run.
By choosing 'Adjust Workflow Template', you then have to activate the event linkage.
but its not getting triggered .. the event which is gettting triggered is not the one whcih is used in the workflow
Thanks for help .
Naval Bhatt

Naval,
Either you can check SAP notes for the same or you can customize the workflow. If the event being triggered is different then copy the workflow and change the workflow start condition.

Print program is not getting triggered when saving the application

Similar Messages

Maybe you are looking for