Hello,

I'm wondering if anyone has code to handle sessions tfacp1140s000 and tfacp1141s000 when you accessed from tfacp1130m000.

I have problems when I want check out the order, so everything is fill properly.

I will check tomorrow - not sure what all we have.

Mark

Some time back I had tried this without success . The reason is tfacp1140s000 starts tfacp1141s000 in the before.program itself. So u do not have an opportunity to handle the subsession. Further tfacp1140s000 is also not available in the list of AFS supported sessions. So we left the AFS route on tfacp1140s000 and settled for manual approval in tfacp1130m000.

Hitesh may be correct. The only place we use the session is in the following code:


stpapi.handle.subproc(sess.acp1130, sess.acp1140, "add")
stpapi.application.option( sess.acp1130, 1, 0, e.msg ) | Approve button
e.msg = "" | "Process gone" mesage OK!

stpapi.handle.subproc(sess.acp1140, sess.acp1133, "add")
stpapi.end.session(sess.acp1133)

stpapi.end.session(sess.acp1140)
stpapi.end.session(sess.acp1130)
stpapi.end.session(sess.acp1110)

Where sess.acp1130 is the tfacp1130s000 subsession. Also if you have one of the source extension programs you could do your own before.program section.

Mark

Since tfacp1130m000 is a main session , it does not have general batch related information. Hence the program tfacp1141s000 pops when used from tfacp1130m000. This is not the case in subsession tfacp1130s000 (as it has the values imported from tfgld1101m000).

We have never tried the subsession approach becos it's a longer route (tfgld1101m000---> tfacp1110s000---> tfacp1130s000) and we don't register invoices through tfacp1110s000 .So Mark's approach may work.