Output types Vs Events

Hi All,
Currently we have a requirement to send an IDOC to warehouse system TMS(Non SAP) from SAP ECC 6.0.
Sales order Creation:They want an IDOC from SAP as and when any sales order is created in SAP. They should receive this information by IDOC so that they can plan for shipping etc..
Sales order change: In case of changes to sales order at header level / Item level, Warehouse system needs to be informed again for the changes done in the sales order. But these change at lines item should be informed to TMS Warehouse only when specific field at line Items are changed like quantity etc.
We are having two solution option for achieving this:
Solution option 1 : Output Type for IDOC
Configuring an output type at sales order for sales order creation and change and then sending IDOC as part of this output type.
Solution Option 2: Configure check and listener FMs for Create and Change Events via SWEC transaction and view SWFDVEVTY1
Listen to event create and change through SWEC and view SWFDVEVTY1 configuration.
In this case we will define our customer business objects and register their events in SWEC for create and change. After these events are registered here, we will go and maintain view SWFDVEVTY1 for receiver types: check and listener FMu2019s.
We are not able to compare the advantages and disadvantages for the two approaches.
One advantage we can see is if we do via event for change then we will not have handle explicitly the changes done to the sales order as these can be defined in the SWEC configuration for change event. But in case of output type, we will have to explicitly handle these changes and write our logic.
We are looking for some more advantages / disadvantages across the two approaches.
If you can provide some pointers in this regard, will be very helpful for us to conclude the solution option.
Thanks in advance for you valuable time and suggestions.
Regards,
Sirisha

Hi Davis,
You are correct. SMFS is stand for Smartforms.
By the way, very good question
Regards,
Ferry Lianto

Similar Messages

Output type not coming automatically

HI
Whenever i am creating using t.code mb11 t.code i have to give output type wa03 manually,is this possible automaticaly output type generation in mb11 t.code
Below settings also i completed
NACE-Select ME Click on Condition records- Select WA03-Trans/Event Type-"WA" Print Version " 2" and Execute it
In the next scren P-1, madium-1, Language EN and enter,, Now select the line and click on the communication method LP01 and save it,,
Regards
sam

Hi
Bijay and nisha thanks for reply still not come my output type automaticaly,i have completed my configuration in omj3 t.code for my plant and storage location.nacz t.code i give 173 GR/GI requirement,
Regards
sam

Automatic triggering of output type in Goods issue

Hello Experts,
I am trying to pick the output type while creation of goods issue document using transaction MB1A. After creation, it is not coming automatically. I did the customization setting for maintaining conditions based on output type WA02, adding trans/Event-WA, print version-3, print item-1 but still it is not populating automatically while creation of GI document.
Could you please let me know, how to do it or if i am missing some customization.
thanks,
Karun

Hi,
To trigger the OUTPUT automatically you have to maintain the CONDITION RECORDS in MN21
Goto the Transaction code MN21 and enter the OUTPUT type as WA02 and give the following details
Trans/Event type
Print version
Print item
partner function
Medium
Date/Time
Language.
After maintaining this check whether the OUTPUT determined automatically or not.
I hope it will determine automatically.
thanks,
santosh

Problems with EventSource generating two different types of event

Hi everybody,
i was trying to connect an EventSource (capable of generating two different event types: a MapEventType and a TupleEventType) to two CQL processors through two separate channels, each one dedicated to its event type:
ASSEMBLY:
<?xml version="1.0" encoding="UTF-8"?>
<beans ....>
     <wlevs:event-type-repository>
          <wlevs:event-type type-name="testMapEvent">
               <wlevs:metadata>
                    <entry key="message" value="java.lang.String"/>
                    <entry key="date" value="java.util.Date" />
                    <entry key="list" value="java.util.List" />
               </wlevs:metadata>
          </wlevs:event-type>
          <wlevs:event-type type-name="testTupleEvent">
<wlevs:properties>
<wlevs:property name="t_message" type="char" length="4000" />
<wlevs:property name="t_date" type="timestamp"/>
<wlevs:property name="t_list" type="object"/>
</wlevs:properties>
          </wlevs:event-type>
     </wlevs:event-type-repository>
     <wlevs:adapter id="input" class="com.bea.wlevs.adapter.example.types.TestAdapter">
     <wlevs:instance-property name="eventTypeName" value="testMapEvent"/>
     </wlevs:adapter>
     <bean id="output" class="com.bea.wlevs.example.types.TestOutputBean" />
<wlevs:channel id="inputChannelTuple" event-type="testTupleEvent">
<wlevs:listener ref="testProcessorTuple" />
<wlevs:source ref="input" />
</wlevs:channel>
     <wlevs:channel id="inputChannelMap" event-type="testMapEvent">
          <wlevs:listener ref="testProcessorMap" />
          <wlevs:source ref="input" />
     </wlevs:channel>
     <wlevs:processor id="testProcessorMap" />
<wlevs:processor id="testProcessorTuple" />
     <wlevs:channel id="outputChannelMap" event-type="testMapEvent">
          <wlevs:listener ref="output" />
          <wlevs:source ref="testProcessorMap" />
     </wlevs:channel>
     <wlevs:channel id="outputChannelTuple" event-type="testTupleEvent">
          <wlevs:listener ref="output" />
          <wlevs:source ref="testProcessorTuple" />
     </wlevs:channel>
</beans>
JAVA:
The com.bea.wlevs.adapter.example.types.TestAdapter class is a simple RunnableBean generating "testMapEvent"s like this:
+public void run() {+
+... bla bla bla ...+
+while(true) {+
Object event = createEvent();
+if(event != null) {+
eventSender.sendInsertEvent(event);
+}+
+}+
+}+
+private Object createEvent() {+
Object obj = eventType.createEvent();
EventProperty p;
p = eventType.getProperty("message");
p.setValue(obj, "Evento #" seqNum); // seqNum is a int+
p = eventType.getProperty("date");
p.setValue(obj, new Date());
p = eventType.getProperty("list");
p.setValue(obj, nipotini); // nipotini is a List<String>
return obj;
+}+
CONFIG:
+<?xml version="1.0" encoding="UTF-8"?>+
+<n1:config xmlns:n1="http://www.bea.com/ns/wlevs/config/application">+
+<processor>+
+<name>testProcessorMap</name>+
+<rules>+
+<query id="testRuleMap">+
+<![CDATA[ select message, date, list from inputChannelMap ]]>+
+</query>+
+</rules>+
+</processor>+
+<processor>+
+<name>testProcessorTuple</name>+
+<rules>+
+<query id="testRuleTuple">+
+<![CDATA[ select t_message, t_date, t_list from inputChannelTuple ]]>+
+</query>+
+</rules>+
+</processor>+
+</n1:config>+
Seems like the events cannot make it beyond the CQL processors:
+<15-dic-2010 20.11.34 CET> <Error> <CQLProcessor> <BEA-000000> <Failed to set property [t_message] of event type [testTu+
+pleEvent]. Cause = [t_message] is not a property of event type [testMapEvent]>+
+<15-dic-2010 20.11.34 CET> <Warning> <Ede> <BEA-000000> <Exception for 'testMapEvent{message=Evento #14, list=[QUI, QUO,+
+QUA], date=Wed Dec 15 20:11:34 CET 2010}' raised by listener = com.oracle.cep.processor.cql.impl.CQLEventReceiver@aa882+
+7+
+com.bea.wlevs.ede.api.EventProcessingException: Internal error processing event [testMapEvent{message=Evento #14, list=[+
+QUI, QUO, QUA], date=Wed Dec 15 20:11:34 CET 2010}] = Failed to set property [t_message] of event type [testTupleEvent].+
+Cause = [t_message] is not a property of event type [testMapEvent]+
at com.oracle.cep.processor.cql.impl.CQLEventReceiver.sendToEngine(CQLEventReceiver.java:389)
at com.oracle.cep.processor.cql.impl.CQLEventReceiver.onInsertEvent(CQLEventReceiver.java:248)
at com.bea.wlevs.processor.impl.EventSenderImpl.sendInsertEventToListener(EventSenderImpl.java:360)
at com.bea.wlevs.processor.impl.EventSenderImpl.sendInsertEvent(EventSenderImpl.java:331)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.eventstore.recplay.RecordPlaySendEventInterceptor.sendInsertEvent(RecordPlaySendEventIntercepto
r.java:159)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.eventinspector.EventInspectInterceptor.sendInsertEvent(EventInspectInterceptor.java:132)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.monitor.internal.MonitorSendEventInterceptor.sendInsertEvent(MonitorSendEventInterceptor.java:4
+79)+
at com.bea.wlevs.channel.impl.ChannelImpl.onInsertEvent(ChannelImpl.java:439)
at com.bea.wlevs.processor.impl.EventSenderImpl.sendInsertEventToListener(EventSenderImpl.java:360)
at com.bea.wlevs.processor.impl.EventSenderImpl.sendInsertEvent(EventSenderImpl.java:331)
at com.bea.wlevs.ede.impl.EventSourceEventSenderImpl.sendInsertEvent(EventSourceEventSenderImpl.java:85)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.eventstore.recplay.RecordPlaySendEventInterceptor.sendInsertEvent(RecordPlaySendEventIntercepto
r.java:159)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.eventinspector.EventInspectInterceptor.sendInsertEvent(EventInspectInterceptor.java:132)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.monitor.internal.MonitorSendEventInterceptor.sendInsertEvent(MonitorSendEventInterceptor.java:4
+79)+
at com.bea.wlevs.adapter.example.types.TestAdapter.run(TestAdapter.java:33)
at com.bea.wlevs.adapter.example.types.TestAdapter$$FastClassByCGLIB$$89b675c7.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:70
+0)+
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.wlevs.ede.impl.EventManagerAccessorProxy.invoke(EventManagerAccessorProxy.java:30)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.wlevs.ede.impl.EventBeanProxy.invoke(EventBeanProxy.java:38)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)
at com.bea.wlevs.adapter.example.types.TestAdapter$$EnhancerByCGLIB$$16190560.run(<generated>)
at com.bea.wlevs.spring.RunnableBeanPostProcessor$RunnableWrapper.run(RunnableBeanPostProcessor.java:117)
at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
+Caused By: com.bea.wlevs.ede.api.EventPropertyException: Failed to set property [t_message] of event type [testTupleEven+
+t]. Cause = [t_message] is not a property of event type [testMapEvent]+
at com.oracle.cep.processor.cql.impl.TupleValueUtils.raiseEventPropertyException(TupleValueUtils.java:153)
at com.oracle.cep.processor.cql.impl.TupleValueUtils.projectEvent(TupleValueUtils.java:90)
at com.oracle.cep.processor.cql.impl.TupleValueUtils.compareAndProjectEvent(TupleValueUtils.java:48)
at com.oracle.cep.processor.cql.impl.CQLEventReceiver.sendToEngine(CQLEventReceiver.java:337)
at com.oracle.cep.processor.cql.impl.CQLEventReceiver.onInsertEvent(CQLEventReceiver.java:248)
at com.bea.wlevs.processor.impl.EventSenderImpl.sendInsertEventToListener(EventSenderImpl.java:360)
at com.bea.wlevs.processor.impl.EventSenderImpl.sendInsertEvent(EventSenderImpl.java:331)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.eventstore.recplay.RecordPlaySendEventInterceptor.sendInsertEvent(RecordPlaySendEventIntercepto
r.java:159)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.eventinspector.EventInspectInterceptor.sendInsertEvent(EventInspectInterceptor.java:132)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.monitor.internal.MonitorSendEventInterceptor.sendInsertEvent(MonitorSendEventInterceptor.java:4
+79)+
at com.bea.wlevs.channel.impl.ChannelImpl.onInsertEvent(ChannelImpl.java:439)
at com.bea.wlevs.processor.impl.EventSenderImpl.sendInsertEventToListener(EventSenderImpl.java:360)
at com.bea.wlevs.processor.impl.EventSenderImpl.sendInsertEvent(EventSenderImpl.java:331)
at com.bea.wlevs.ede.impl.EventSourceEventSenderImpl.sendInsertEvent(EventSourceEventSenderImpl.java:85)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.eventstore.recplay.RecordPlaySendEventInterceptor.sendInsertEvent(RecordPlaySendEventIntercepto
r.java:159)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.eventinspector.EventInspectInterceptor.sendInsertEvent(EventInspectInterceptor.java:132)
at com.bea.wlevs.ede.spi.AbstractSendEventInterceptor.sendInsertEvent(AbstractSendEventInterceptor.java:78)
at com.bea.wlevs.monitor.internal.MonitorSendEventInterceptor.sendInsertEvent(MonitorSendEventInterceptor.java:4
+79)+
at com.bea.wlevs.adapter.example.types.TestAdapter.run(TestAdapter.java:33)
at com.bea.wlevs.adapter.example.types.TestAdapter$$FastClassByCGLIB$$89b675c7.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:70
+0)+
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.wlevs.ede.impl.EventManagerAccessorProxy.invoke(EventManagerAccessorProxy.java:30)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.wlevs.ede.impl.EventBeanProxy.invoke(EventBeanProxy.java:38)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)
at com.bea.wlevs.adapter.example.types.TestAdapter$$EnhancerByCGLIB$$16190560.run(<generated>)
at com.bea.wlevs.spring.RunnableBeanPostProcessor$RunnableWrapper.run(RunnableBeanPostProcessor.java:117)
at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
+>+
Can anybody help me figuring out what's wrong?
Thank you in advance!

Hello Chris,
Wondering if you've found a solution for this.
I was thinking you could make a web app that used the jQuery dialog, then let the client just put an individual web app item on the home page when they want to have the pop up.
This way it is more like one type of modal window and the client can show whatever they want when they want, and turn it off by removing the module.
You can place the module inside a content holder so they do not mess up any template or page content.
Hope this helps,
Chad Smith | http://bcgurus.com/Business-Catalyst-Templates for only $7

Material document "Output type".

Hi,
after setting the system with the following parameters (trx MN21):
Output type: WE01,
Trans/Event type: WE
Print version: 1,2,3
Print item: 6
Output type: WE02,
Trans/Event type: WE
Print version: 1,2,3
Print item: 6
Output type: WE03,
Trans/Event type: WE
Print version: 1,2,3
Print item: 6
output types WE01, WE02, WE03 are not created automatically
What is the difference between print item 1 and 6 ?
Can't understand why
Best regards

hi,
maintain one output type we03 thru transaction mn21 with the following data
Event type:WE
Print version :3
Print indicator: 1
assign the output type to the printer.
1- material document print out
6- GI/ GR Document print out
Regards,
velu

EDI/ALE-Output type-Process code relation?

Hi.
In EDI preocessing the relation between the Message type and the process code is know.
But where is the realtion of either of these two to the output type?
When we hit a F4 in the message control in WE20 for process codes it gives us a list.
How is this linkages established.
Output type-process code-message type-output routines?
Please dont answer in vague terms.

Dear experts,
I am a little further now.
I used output condition WA01 which is already set up in NACE and in MN23 I set up:
In SP01 I can see the created Spool entries after creating the Good issue with ME2O. So the print out would work. But I need an EDI output....
I created a new output condition ZWA1 in NACE and set "Processing routines" to EDI.
I set "Partner functions" to EDI and LS - logical system.
In MN23 I have:
I set Event Type to "WA" because when I look at a material document in MB03 it also shows WA:
In WE20 I have my LS - logicals system and set up the output for MBGMCR03:
What confuses me is: I have to send the EDI output to a LS - logical system. But in MN23 I can't set the LS - it gives error: "You cannot enter a partner function for output ZWA1"
No IDoc is created so far - please help. Thank you.
Best regarsd,
Peter

Medium in output type

Dear all,
I'm in the midst of figuring how ALE being sent out via message control. While looking at a Sales order's output type setting screen, under Medium column it contains:
1. Print output
2. Fax
3. Telex
4. External send
5. Simpal mail
6. Special function
7. Events(SAP business workflow)
8. Distribution(ALE)
9. Task (SAP business workflow)
For my case (send IDOC via ALE), i know that i have to pick option Distribution(ALE).
But apart from that, may i know how Telax, External send, Special function, Events and Task work?
Thanks.

HI,
If you chose other options, the driver program that you configure the SPRO or NACE, will get triggered.
In the driver program, logic must be written in order information is processed (It can be sent as Telex, Mail, Fax based on the SCOT settings and SAP Connect settings).
If the option you chose is Special function, the driver program may or may not send any mail/fax but you can do any processing . For example, if you want to update a Z Table on issuing the output, you can have that logicn in the Z program and have that attached to the output type in NACE transaction.
REgards,
Ravi

Output type for gr/gi slip

Dear all,
I have done GR for two line items in MIGO and i have ticked the printing for gr/gri slip in general tab of hearder.
But if i go and check the MB90 for the print , system show only one line item GR/GI slip.
What may be the case , i missed . so GR/GI slip is not get printed for the 2 line item
i have selected individual slip in MIGO and i have the maintain the output condition record for the gr/gi slip as
trxn : NACE
application : ME
output type : WE03
trans.event type : WE
PRINT VER : 1 ( INDIVIDUAL SLIP)
PRINT ITEM : 1 (MATL DOC PRINT) FOR THE PLANT XXXX.
Pls tell me if any setting i missed or wronly updated
Thanks
v braj
Edited by: raj on Mar 4, 2011 10:00 AM

Hi there
Select the PRINT VER : 2 ( INDIVIDUAL SLIP) and reprint,,
Thanks
Senthil

Blocking Output types from Triggering.

Client has a requirement that if overall credit status of delivery is 'B' ( Blocked ) then all output types Automatic or Manual associated with the delivery should be blocked.
I added following lines of code in requirements for all output types associated with deliveries
IF   KOMKBV2-CMGST CA 'B'.
    SY-SUBRC = 4.
    EXIT.
ENDIF.
But we are still able to attach output types to deliveries with credit status blocked, any pointers ?

hi Saket,
This can be the issue you are facing.
you are exiting from the current event with the 'EXIT' statment, but the validation is not applicable in the subsequent event.
in the subsequent event, may be 'END-OF-SELECTION',
insert the following statement, as the first statement:
CHECK NOT KOMKBV2-CMGST EQ 'B'.
hope this helps

Workflow triggered twice. Triggered using Message Control/Output Types

I created an output type for VA01. After creating (then saving) SO, workflow is immediately triggered which shouldn't be the case since I have to run program 'rsnast00' to trigger workflow. So workflow is triggered twice during the process. How do i fix this?
DATA:
dispatch time = 'send with periodically schreduled job'
application = 'v1'
transmission medium = 'events'
processing 1
program = 'RSWEMCO1'
form routine = 'CREATE_EVENT'

May be the workflow is triggered in such a way that when ever out put type is created then the workflow must be triggered.
As the purpose of the report stated by the SAP is
Purpose
Issues output from all applications with send times 1 and 2.
May be the output type is created twice but the output of the report is not Duplicated. ( mentioned by SAP ) check the documentation of the report.

Two output type

Hi Gurus,
I've a typical issue here.
I've two output types for sales order .Maintain condition record ,access sequence,VOFM routines individually perfectly for both output types.
1st output type - no multiple issue..(maintained in NACE)
2nd output type - multiple issue.(maintained in NACE properly)
While creating order both outputs are issued(fine).
But while changing order, 2nd output type has to be issued but its not.
When I debugged , its looping the entries already present in NAST table.(checking the first output type for multiple issue)
its not and then its completely coming out of the program without checking the second output type for multiple issue.
Is there any extra settings I've to do or its SAP bug.
Regards,
Ponraj.s.

Hi,
There are two options.
First is, use the same output type for all the movement types. Iin the smartform itself you can put conditions
based on movement type to call a particular window.
Other options is in SPRO->Materials Management->Inventory Management and Physical Inventory->Print Control
->Maintain Print Indicator for Goods Receipt Documents. Maintain different indicators for 102 and 122 (For ex. 2)
Then maintain the condition record for the output types WE02 and ZA01 accordingly.
Maintain output type WE02 for Trans./Event Type - WE, Print Version - 1 or 2 or 3 and Print Item as 1.
Maintain output type ZA01 for Trans./Event Type - WE, Print Version - 1 or 2 or 3 and Print Item as 2.

Triggering workflow through MIGO in output type

Hi Friends,
After the GR Documents are posted, I need to Trigger GR Workflow......
Please guide me any Function modules or BAIDs
to keep our code once the MKPF and MSEG DB Tables are updated with recently Created new Documents....
Can we Assign our Workflow Template in the OUTPUT Type in NACE.
If so, Please Guide me with the OUTPUT Type configuration Steps
Thanks in Advance,
Ganesh

I think you can use standard Buiness object BUS2017. While creating the document please check which events gets trggered in SWEL. I am sure the Created event of this Business object gets triggered.
Thnaks
Arghadip

IM output types

Dear MM Consultants,
I want to knoe the differance between the following output types.
WE01/0/03 WA01/02/03
My reqt is i want to print morethan 1 item in GR/I print out.
I made all setiting in OMBr/ NACE/Mn21etc...
Still i am not getting the output
One more qn
Can we use we01 for collective slip??
pl reply
guru

Guru,
You should have all of the following settings:
1. Configure Print Control for transaction MIGO:
>SPRO: Materials Management > Inventory Management and Physical Inventory > Print Control > General Settings > > Print Version
>
>Tcode = MIGO
>P = 3 (Collective slip)
>
>This will set the default selection on the MIGO screen to "3" (Collective Slip)
2. Configure output Type
>SPRO: Materials Management > Inventory Management and Physical Inventory > Output Determination > Maintain Output Types
>
>Output type = WE03
3. Configure Output Determination Procedure
>SPRO: Materials Management > Inventory Management and Physical Inventory > Output Determination > Maintain Output Determination Procedures > > Conditions: Procedure
>
>Condition Type = WE03
>Requirement = 173
>
>Requirement 173 limits output to be generated for the first item only (even If you want all line items to print on the same GR slip - you only want the output record to be created once - not for each line. 173 does this for you
4. Create Output Condition Record in each client in Tcode MN21
>Output type = WE03
>Trans/Event Type = WE (Goods Receipt for Purchase Order)
>Print version = 3 (Collective slip)
>
>If you already have WE03 set up with settings other than described above, you may need to delete it first and then re-create it using the information above.
5. If all of the above settings are correct and you still do not see all line items on the same GR slip, then I would consult your developer to see if they changed anything in the Output program, Routine, or the SAP Script/SmartForm

Output type for production order

Hi, when we save the production order, we wants to transfer the prod order header details in legacy system thru idocs. Trying to define output type for production orders in NACE t-code, could not find production order option there. Pls advise in this case how to define the output type for production order so that the header data will be taken by idoc and transfered to legacy. Pls advise.

Hi,
production orders don't have output types like SD orders.
But they have status control and events. Look into the object type BUS2005 in transaction SWO1. There you find the events which are fired by SAP, eg. ProductionOrder.Released.
Which Idoc type do you want to use?
I think you have to programm your own method for the Idoc creation. Put it into a workflow task and assign it to the event.
Regards
Michael

Diff. between PPF and OUTPUT TYPES

hi,
can anybody tell the exact diff. bet.PPF and OUTPUT TYPES.
ppf is the advance method of output types.
could anybody pls explain breifly

Hi
Post Processing Framework allows you to process actions for different output types such as printing, sending emails, or faxing using Smart Forms. Since SAP applications work on the document concept (i.e., they generate documents for key business events or processes), they can also trigger a workflow or user exit to perform functions based on the conditions you configure. This technology replaces the output control in R/3 with a wider functional scope that is simple to maintain, use, and connect to another SAP system, a non-SAP system, or any other subsystem.
Post Processing Framework (PPF) technology is a uniform interface available since SAP R/3 Enterprise Release 4.7. Part of the SAP Web Application Server (Web AS), PPF can trigger workflow for email, fax, and print, or can call another method, such as sending data to another subsystem. The actions are based on the conditions that you configure.
PPF has tools for scheduling, starting, and monitoring actions. Determining, generating, and processing actions can either take place automatically or with user interaction. A condition trigger could be a preset condition the system can look for, such as a price higher than a certain amount, or it could be based on a user action, such as an approval in the case of workflow.
Im going to show you how to set up actions that trigger application documents. The system supplies some samples, so you can use Copy with Reference and make your own changes to predefined configurations, or you can take the approach of creating your configuration from scratch using the wizard. Ill explain the two methods:
Create and modify PPF directly in the Web AS configuration in the application area. Ill start with the customizing steps, as they explain the configuration from the application point of view.
Create a PPF definition using the wizard, a quick setup tool that focuses on the technical setup of the PPF. Using a wizard, you get the same results in terms of the technical settings for the PPF configuration as if you had used the configuration steps directly. The wizard provides application area detail and pre-populated information and it is the best practice. It can help when you create a new action that differs widely from those you already have.
The wizard, however, helps you perform the definition only you must do other associated configurations directly in the application area.
Visit the below link for more info..
http://help.sap.com/saphelp_crm40/helpdata/en/b3/58bf39f7568648e10000000a11402f/content.htm
Regards
Suresh

Output types Vs Events

Similar Messages

Maybe you are looking for