BADI PROCESS_PO_CUST is not triggered from APO tcode /n/sapapo/snptlb

Hi ..
We are using BADI : PROCESS_PO_CUST to make Client Specific Changes and is Working Fine in R3.
But While create PO in APO Via transaction(/n/sapapo/snptlb) this BADI is not triggered.Please let me know if you have any inputs on the same
Cheers
Mukundan.R

Solved. Thanks to ABAPOne.
Referring to: FIELDSELECTION_ITEM method in ME_PROCESS_PO_CUST Badi

Similar Messages

Purchase order creation triggered from APO diferent from one created in ECC

Hi All:
When you check the 'Conv. Ind' against a purchase requisition in /SAPAPO/RRP3 it triggers conversion of PR to a PO in ECC. The problem is, the PO created this way does not have a tax code in the PO item> Invoice tab in ECC. But if I try to convert the same PR to PO using transaction ME21 or ME21N in ECC this field becomes mandatory. Question is , is APO trying to use a different transaction. If so, how do I find out what it is?
Pl help.
Thanks
Ryan

Thanks for your reply Sreeni:
I understand the process of PO creation triggered from APO is automatic. But what is the setup needed to automate it? Is the setup in ECC or APO or both? Where do you setup which PO creation transaction to trigger in ECC to create a PO triggered by APO? Pl. let me know.
Thanks
Ryan

BADI / User Exit for APO Order transaction /SAPAPO/SNPTLB

Hi Experts,
We have a proxy interface and currently we are using FUNCTION EXIT_SAPMSNPUSER_006 for the APO Order transaction: /SAPAPO/SNPTLB.
This exist is triggering before the Order is being saved in APO and at times it is throwing an error 'Order key already exists in live cache' in the APO system.
Is there any other BADI or User exit available to Save the order in APO before the interface gets processed?, if so, plese guide me.
Thanks & Regards,
Vijaya

Hello Lakshmi,
I am having the same issue with the message "Order key already exists in live cache" in our system.
We are using the user-exit EXIT_SAPMSNPUSER_005 for UoM conversion. But we are not making any explicit proxy calls
to /SAPAPO/SNPTLB. Does the system automatically call this transaction with this user-exit?
Did you get a resolution for the issue. I would really appreciate if you can let me know how you have addressed this.
Thanks,
Ratnam

What are APO orders in APO (APO Order transaction:-SAPAPO/SNPTLB)?

Hi Experts,
Basically, am ABAP developer, but, i got a statement as below, regarding the APO,
User Exit of EXIT_SAPMSNPUSER_006 was used for the APO Order transaction:-SAPAPO/SNPTLB.
- What is the APO Order transaction:-SAPAPO/SNPTLB?
- What are the APO orders? Are they are planned orders, like PLNUM field in PLAF tbl?
- Why this transaction is used?
- What could be the business requiremnt behind this development?
- Any other info?
If my question is wake, sorry! Replies are gretaely appreciated.
thanq
Edited by: SAP ABAPer on Mar 29, 2009 7:09 PM

Hi,
Transaction /sapapo/snpylb is a transaction for Transport Load builder.
It does an optimised load build.
It is used to create transport loads once the deployment is carried out.
Once the load is created and you hit save, the user exit EXIT_SAPMSNPUSER_006 gets called.
When one creates the load, APO assigns an internal no to the id.
We had used this user exit to generate a custom no once the user hits save.
Hope you find this information useful!

2010 Publishing Approval Workflow not triggered from Office 2010 application

I have a peculiar situation to which I have been Googling for weeks now but to no avail.
Basically, I have configured a publishing approval workflow to fire when the user checks in a word document as a Major version. I tested it and all was fine. I later found that on a select few PC's on the office network the prompt (workflow initiation
form) was not popping up when checking the document in via the office 2010 word client and therefore the workflow wasn't being initiated.
I have gone down many avenues of group policy, SP permissions, AD settings, even reinstalling office but nowhere nearer to solving the issue.
Please bear in mind I have it configured correctly from a SharePoint point of view i.e. checked the box to allow workflow to be manually started & start to approve publishing on major version.
This might be a clue: it works when checking in via SharePoint but not when checking it in via word, therefore indicating a desktop client or office issue.
Does anybody have any knowledge of what triggers the initiation form to fire and what might block it or not register its existence from an office app point of view? Any general comments would be welcome.
Spec of problem machines: - Windows 7 (x32/64), Office 2010 Std, SharePoint 2013 server (but using 2010 workflow in this case).
Marc Grocott

Hi Marc,
Based on your description, my understanding is that when you check in a major version from word, the workflow initiation form not appear.
In order for Document Approval workflows to work seamlessly with word, you can tick the option: "Allow this workflow to be manually started by an authenticated user with Edit Item Permissions".
Here is a detailed article for your reference:
Approval workflow does not start from Microsoft Word
Best Regards
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Zhengyu Guo
TechNet Community Support

Mappings not triggered from Process flow?

Hi,
I have some mappings under a process flow..they are triggered daily but today they were not triggered can anyone tell me how to go about this?

Hi ,
If you have deployed the schedule then it will be in Disable state .
You can check that by logging into SQL*PLUS as the Target user and running
select job_name, state from user_scheduler_jobs;
Use the Schedule tab on the Control Center Jobs panel in the Control Center Manager to schedule
the job. Highlight, right click the job and from the pop-up menu select "start". Use the same query to check the current status:
select job_name, state from user_scheduler_jobs;
The above query will show whether the scheduled job is SCHEDULED, RUNNING or SUCCEEDED.
Thanks,
Sutirtha

BADI ME_PROCESS_PO_CUST is not triggering while creating/changing PO

Hi,
I am new to BADIs,
I am trying to implement BADI ME_PROCESS_PO_CUST in ECC 6.0. I have done the implementation and activated. I kept a break point in PROCESS_ITEM method, but the BADI is not triggering while creating or changing the PO. Please advice me what could be the reason behind this?
I used the SQL trace but i couldn't get the BADI ME_PROCESS_PO_CUST in the list.
thanks in advance
Regards
Jagadish

hello jagdish,
implement this user exit.....
MM06E005...
go to EXIT_SAPMM06E_017 in that then you can put a break point in the user defined function module.....
or use
BREAK 'C5133392' (use your user in place of C5133392)....it will stop here while creating PO or changing PO...
now you can do whatever you want to do in create or change PO using this function exit......
perform the validations on import parameters.....to create or change ....and activate the project....
hope this will give you some idea and help

Central Contract Mngt: Contract Confirmation Out not triggering from ECC

Hi,
Can some one take a look at this and let me know if you have any suggestions
After following note 1268821 we have Contracts replicating from SRM to ECC via PI. However we are not getting the Contract Replication Confirmation Out triggering from ECC to SRM The configuration in PI is waiting to receive PurchasingContractSRMReplicationConfirmation_Out from ECC for delivery to PurchasingContractSRMReplicationConfirmation_In in SRM.
Does anyone know what we maybe missing, perhaps a setting in ECC that will trigger the Confirmation Out to SRM?
Any help much appreciated.
Che

Just an update.
It turns out that ECC is generating message PurchasingContractERPConfirmation_Out which is contrary to what we are expecting PurchasingContractSRMReplicationConfirmation_Out.
Have logged it with SAP support for now.

Validation on line items not triggering for MR41 tcode

Hi,
I have to put a validation on MR41 to check the amount entered on the screen. I am using OB28 to define the validation. Also, I have created user exit in the validation/substitution program where the necessary checks are done. But the validation is not triggering at the line item level. I have another validation of MR41 at header level, that is working perfectly. I want the validation to trigger at line item level also.
Any ideas on how to do it?
Thanks in advance.
Regards,
Arun Mohan

Hi,
Try with user exit MM08R002 under this u can find thease exits.
EXIT_SAPLKONT_002
EXIT_SAPLMR1M_001
EXIT_SAPLMRMC_001
<b>Reward points</b>
Regards

Help, CCX7 not triggered from outside, codec problem.

Good Day..
Here we have a scenario that is, a customer upgraded from CUCM4.2 and IPCC4 to CUCM7.0 and CCX7.0, in the old deployment, he used codec G.729 on IPCC and for sure for the voice prompts, and it used to work fine, now, after the upgrade, and using the same script, prompts and choosing G.729 to run on CCX, we are only able to listen to prompts and go into the AA menu options internally, but when calling from outside, nothing, it keeps ringing.
I changed the codec back to G.711 from CCX’s service parameter, and called from outside, the CCX opens the script yes, but not playing any prompts…
Although the gateway used to work with IPCC normally, I had configured codec G.729 and ran it under a special dial-peer dedicated for CCX trigger DN, still nothing changed..
Any guides please.
AT

Does not matter if you are using MGCP or H323 the same rule applies for xcoding needs. The bigger question is what has changed as part of the upgrade as there should be no changes from operations point of view.
I would suggest checking if there are media resources such as Xcoder that for some reason did not register after the upgrade. Also, is the site with the GW experiencing the issues remote from the UCCX server? If you want to use G729 for calls into the GW simple change the region assigned to the GW's DP to use G729 between itself and the UCCX cti ports.
HTH,
Chris

SRM - BADI Method is not triggered in background

Dear Experts,
In our SRM system we are trying to use an implementation of BADI BBP_DOC_SAVE_BADI method BBP_DOC_SAVE to automatically modify bid invitations at save time.
This works fine when the Bid invitation document is created directly in foreground but doesn't work when it's created in the background in workflow via a request/shopping cart.
Does anyone know about this,are we using the wrong BADI or is anything else missing?
Thanks in advance!
Anders

Hi,
Thanks for the reply on the post.
I have similar requirement but can not use BADi as this is obsolete, can you please suggest the approch in details as we have not worked on Web Dynpro.
Also if the BADI BBP_F4_READ_ON_EXIT is obsolete, does SAP provided any other BADI which can be used for the same purpose?
Please clarify, Any help would appreciated.
Thanks a lot in advance.
Regards,
Abnish Jain

Demand not transferred from APO to R/3

Hi All,
We had a daily batch in which forecast is released to R/3.
This problem is sporadic. For some materials the data is not
transferred to R/3 during batch job and then if we transfer it
manually again. It gets transferred.
Also we see lot of Queues in SMQ1 with status SYSFAIL and message "Material status does not allow a planned independent requirement"
We have activated the Queues and unlocked it to process but still they are not processed.
Can any one let us know because of the blocked Queues only the data transfer is not happenning to R/3?.
Thanks in advance.
Kumar

Hi Kumar,
As you have rightly confirmed that master data is not an issue
Moreover you have also confirmed that issue is happening
sporadic and not reproducable.
Your symptom indicates that there could have been inconsistencies
in system.
I would suggest carry out an integration model run and transfer
all master and transactional data.
Then try carrying out CCR run (if possible also om17) and then
iterate all the inconsistencies
Then the most important step to do is to clear all the queues.
Ensure that before start of the batch jobs, there are no errors
or hanging queues in system
This will remove the error. Just try this and confirm
Regards
R. Senthil Mareeswaran.

BADI/User Exit for APO Transaction: /SAPAPO/SNPTLB

Hi Experts,
We have a proxy interface and currently we are using FUNCTION EXIT_SAPMSNPUSER_006 for the APO Order transaction: /SAPAPO/SNPTLB.
This exist is triggering before the Order is being saved in APO and at times it is throwing an error 'Order key already exists in live cache' in the APO system.
Is there any other BADI or User exit available to Save the order in APO before the interface gets processed?, if so, plese guide me.
Thanks & Regards,
Vijaya

Hello Lakshmi,
I am having the same issue with the message "Order key already exists in live cache" in our system.
We are using the user-exit EXIT_SAPMSNPUSER_005 for UoM conversion. But we are not making any explicit proxy calls
to /SAPAPO/SNPTLB. Does the system automatically call this transaction with this user-exit?
Did you get a resolution for the issue. I would really appreciate if you can let me know how you have addressed this.
Thanks,
Ratnam

Provide Input Parameters when called only from a TCODE

Hi Experts,
I have a requirement where in we need to provide a input parameters for a report when it is triggered from a TCODE.
When this program is executed in SE38, the input parameters should not be available. The report takes a default value which is
defined in the program.
We need use the same program when called using the TCODE, as well as from SE38.
Looking for a early response.
Thanks in advance.
Regards,
Kumar.

>
saravanau wrote:
> The program willl be scheduled everyday which will take the default date.
In case of Background processing SELECTION-SCREEN will not be displayed so you don't have to worry about it.
For retriving data for a particular date i need to provide user input screen. This will be done through ZTCODE.
You would schedule the job on a daily basis in SM36 & for individual dates you'll access the report via the T-Code. So where does SE38 come into the picture?
@Marcin: If SY-BATCH = 'X', i don't think SELECTION-SCREEN will be available
BR,
SUhas

Shipment output not triggered...

Hi, I tried to find solution for this in forum, but could not... In my case,
When user creates a shipment using VT01N/VT02N and clicks the planning button and then clicks on save button, I need a custom idoc to be sent to SAP PI.
I tested sending this idoc from WE19 to PI and it is working fine...
But the output type is not triggering from VT01N/VT02N. I am not sure which of the config setting is wrong. Can someone point out which setting is missing/may have issues.
Also, I did an output determination analysis and it shows me a green entry which means it chose the custom output type and related access sequence. But then why is idoc not generated. I have put a break point in the custom function module in which I populate the custom idoc segment.
Please help to fill in the gaps ...
1. I checked in NACE, under V7 - Transportation, there is my custom output type ZEDI, with partner functions set as
EDI - LS - Logical system
EDI - CR - Carrier
I am not sure if this is correct !!
Processing routine points to RSNASTED, EDI_PROCESSING.
I checked the condition records tab...
The shipment type ZOUT is configured there, with one entry
ZOUT - DESCP - LS - logical system name i.e. PI system name - medium as 6.Date/Time as 3.
Again I am not sure if this is failing !!
Procedure tab does not have any entry related to this.
Access sequence also does not have any entry.
The partner profile (WE20) entries as as follows;
for the PI partner, Partner role is LS, message type is SHPMNT, under outbound params.When I double click that I see receiver port set, basic type has custo idoc name, Message control tab has V7 - ZEDI - process code ZSSS. And that process code is bound to the custom function module where I fill the idoc segment.
But finally I do not see any idoc generated !!
Please advise.

Hi ,
1. Does the condition record is automatically pulling up in the Vt02n transaction or no ?
2. Try first checking the IDOC trigger with the Standard Process Code SD11 to see if the Output Determination is working correct. Once u know that part then the partner profile setup to check with the Process Code ZSSS, whether the output is being determined or not. Based on the same atleast u can narrow down the root cause.
Are u working on this Interface for a Advance Shipment notification to the customer ?
Cheers
Balaji

BADI PROCESS_PO_CUST is not triggered from APO tcode /n/sapapo/snptlb

Similar Messages

Maybe you are looking for