cancel
Showing results for 
Search instead for 
Did you mean: 

new workflow event in condition records for schedule aggrements

former_member183924
Active Participant
0 Kudos

Hello Experts,

<h2>My goal</h2>

if a forcast schedule is generated (via ME38 --> Generate Forc. Schd. F6) for output (print or EDI), I want to trigger it and make some additions to the internal tables.

I think this could be realized with Message Control tool. So that I can mantain the output types for events via the condition records (MN11 - Purch. SchAgrReleas).

<h2>Problem</h2>

To maintain the conditions is not a problem via MN11. But if I want to insert my new Business Object type with the new event for the communication details, the error message "Object type ZBUS201302 is not assigned to application EL"

Message no. VN350

Table: T681Z

I could assign the standard BO BUS2013, because this is assigned to the application EL. But not even the standard BO BUS2013002 works here... it is also not assigned to EL like my new one.

<h2>Detailed description</h2>

-created my own business object ZBUS201302 (cos the standard object BUS2013002 doesn't has events included) as subtype by BUS2013002.

-added a new event "Created" (this own is my event if a new forecast schedule is generated)

-maintained all aspects in NACE (message controls tool): roles, message relationship; output program: RVNSWE01 with form routine CREATE_EVENT; partnerroles

*procedures

*output types

*access sequences

*condition records (but without the right communication setup)

--> the custoizing checks (NACE --> Goto --> customizing checks) doesn't report any errors for the new

Best regards

Steffen Froehlich

Accepted Solutions (0)

Answers (1)

Answers (1)

pokrakam
Active Contributor
0 Kudos

Hello Steffen,

Just to ask the obvious: Why workflow?

Can't you just call a FM via message control or use a BAdI?

Cheers,

Mike

former_member183924
Active Participant
0 Kudos

Hi Mike

I know , I already found the right FM: EXIT_RM06EFAB_001

But FMs are obsolet since R3 4.6 and we have now ERP 6.0 :)...

The only BAdI I found is ME_PURCHDOC_POSTED.POSTED, but I'm not so familiar with BAdIs. I already implemented one small workflow...

Thanks,

Steffen

pokrakam
Active Contributor
0 Kudos

LOL, so you don't want to use FMs because they are obsolete but don't want to use BAdIs because it's new and unknown!

Seriously though, as much as I'd like to promote workflow, I think it's overkill here...

Cheers,

Mike

former_member183924
Active Participant
0 Kudos

Hi Mike,

I don't want to use BAdIs, cos there are unkown for me and I have to solve the problem here. I'm open for new things every time :).

So I'll try the BAdI, I hope further maintenance are easier to do.

BTW: I solved the problem for my business object and the error msg. VN350. I had to delete the 3 last attributes in my ZBUS201302. Then the keys for the condition table and the BO match.

Do you have one good site for learning BAdIs (like a tutorial)?! I just found: http://www.saptechies.com/simple-sap-badi-example/ for now.

thanks, regards,

Steffen

former_member183924
Active Participant
0 Kudos

In ERP 6.0 we have the new Enhancements technique in there. But I think I use the classic BAdI implementation, cos the new one seems also a little bit oversized?!

Thanks,

Steffen

pokrakam
Active Contributor
0 Kudos

If you're in a hurry, just use the regular userexit.

Otherwise classic BADIs are very simple: SE19 -> select BADI, click on create implementation, give your implementing class a name, add code and activate.

Enhancements are not complex either, they're quite well documented in the online help too. the tricky bit here would be finding the right place to put your enhancement, so I'd go with the first two options.

Cheers,

Mike