Stop PO idoc

Based on a condition, I need to stop a Purchase order IDOC (orders05) from being generated.. Any ideas?

Hi Krish,
Subroutines KOBED_101 is used for condition check for condition type level.
Subroutines KOBEV_101 is used for condition check for condition type exists.
For more information on logic, please check program SAPLV61B.
Hope this will help.
Regards,
Ferry Lianto

Similar Messages

Stop Inbound IDOC's from being created

I want to stop inbound IDOC's for a particular partner (type LS) from being created in our R/3 system. Is there a way to do this? I am aware these can be stopped in the middleware, but this is not possible in our case. I am also aware that I can stop these IDOC's from being processed via the partner profile, however, there will be a huge number of useless IDOC's that will be created in our system and I want to avoid that.
Hence, I do not want the inbound IDOC's to be created in the first place even though they are transmitted to SAP. Is this possible?
Any inputs will be highly appreciated.
Thanks,
Raghu.

Hi Satwik,
Choose Idoc in WE02.
Get port name, Then in WE21 get RFC name.
Go to transaction SMQS - Here we can block this RFC instead of blocking the queue.
Thanks,
Anil

Can we stop incoming IDOC in XI

In a particular XI scenario, IDOC is coming from a R/3, but due to some performance reason, we need to stop those IDOCs entering into XI,
i am not supposed to change the Configuration, or Design in Integration builder (due to some reason),
also, we cannot stop those IDOC from R/3 (due to some reason),
How can we stop these IDOCs flowing into XI,
is there any facility in IDOC adapter to filter those particular IDOCs,
pls advice

Dear Sudeep,
I'm not sure what exactly is your performance issue.
If you dont want specific IDocs send to XI from R3 you should remove it
from the Destribution model (BD64)
and\or from the partner profile (WE20).
best of all is to remove the action from the customization that initiats calls for th ALE output type.
consul your SAP R3 uisness pepole or your ALE specialist.
Nimrod.G

How to stop outbound IDOC in PI without error

Hi,
The scenario is Idoc - JDBC and personID is unique field in database.
Now the requirement is, in some cases personID generated after certain process or I can say in some cases personID is not present when this interface runs.
Now I need to stop outbound Idoc in PI system (without any error) if perosnID is not present. Means I dont want to send any data to database if personID is not present. Is there any way to accomplish this task?
Regards,
Chintan

Hi All,
Thanks for replying with very useful information and answers, really appreciated.
I am able to solve this issue by using Node Function at Message Type level. I created following condition at message type level.
personID -> removecontext -> Equals -> 0001 -> removeContext -> createIf -> receiver MT
Here i've to use removeContext two times because the segment which contains personID field is repeated many times so I've to check in each segment.
If this condition fails (if personID is not present ) then the target message structure is not going to be created.
Thank you once again.
Regards
Chintan

How to stop an idoc from being processed further

Hi Experts,
I have a requirement where i have to stop the idoc from being processed in an user exit.
I have to stop the idoc and give a suitable status message over there.
It would be highly helpful if anybody tells me how to stop the idoc abruptly and giv the status messsage.
Thanks in advance.
Praveen.

Hi,
Check the below link
https://forums.sdn.sap.com/click.jspa?searchID=11810720&messageID=3032674
You need to find aproper EXIT.
The avaliable options for you in the exit is
IDOC_DATA
Now if i pick the segment having shiped qty from the data record and check the same with the delivery qty your objective is half done.
When the condition fails you need to update the IDOC with Error 51 saying that this is not possible .
for that you need to bring your logic as
LOOP AT IDOC_CONTROL.
PERFORM LOGIC...
ENDLOOP.
FOR LOGIC .
All the criteria and then update the status of the IDOC then error is generated and updated to the IDOc.
PERFORM updatestatusidoc.
endform logic.
like this in
form updatestatusidoc.
IF subrc = 0 .
t_idoc_status-docnum = f_idoc_contrl-docnum.
t_idoc_status-status = c_idoc_status_ok.
t_idoc_status-msgty = 'S'. -
>denotes success
t_idoc_status-msgid = 'ZXXX'.
t_idoc_status-msgno = '000'. "
t_idoc_status-msgv1 = itab-field.
APPEND t_idoc_status.
ELSEIF subrc = 1.
t_idoc_status-docnum = f_idoc_contrl-docnum.
t_idoc_status-status = c_idoc_status_error.
t_idoc_status-msgty = 'E'. "denotes --->error
t_idoc_status-msgid = 'ZXXX'.
t_idoc_status-msgno = '001'. "
t_idoc_status-msgv1 = itab-field.
APPEND t_idoc_status.
endif.
endform.
this has to be done to make the idoc to trigger error mode.
Regards,
Raj.

Looking to stop sending IDOC if output has been already processed for PO

Hi,
I am using the Message type ORDERS to trigger the IDOC for the purchase order based on the output type. But my requirment is that if the output is already processed for a specfic purchase order then it should not allow to process the output again for that purchase order. So i am writing a logic in user exit that if NAST table entry is already exist and proccessed for the output type for specfic purchase order then i want to stop sending the idoc. As NAST entries doesn't contains any segment data due to that i am unable to set the ALE filter in BD64 transtaction .So could you please anyone give me any suggestion how can i stop sending the IDOC if output has been already proceessed so that it will helpful for me.
Thanks in advance for your help .
Regards,
Kiran

>
divyesh vasani wrote:
> Hi Shabarish,
> Thanks for your reply.
> I was working on solution proposed by NALLAM GUNA RANJAN.
> But as you and Jai mentioned, but I think Maintain Order At Runtime option is available with Interface determination not with Receiver determination.
> In my case, From same Input file(from which Text file is generated) mail report has to be generated but after creation of text file only.
>
> Thanks
> Best Regards,
> Divyesh
1. In case you intend to use maintain runtime then use a single receiver and add multiple inbound interfaces. This is the easiest solution
2. use a BPM. use send steps in serial. First send step should be File (request for acknowledgment) and then followed by send step for mail.
Do not go for scripts etc unless no other solution persists since maintenance and support in the future will always be an issue.
let me know if u still have issues.

How to stop the IDOC adapter using IDPI framework (APIs)?

Hi Guys,
We have a requirement to start/stop the communication channels depending on the Integration scenarios. But for IDOC and HTTP we dont have any sender channels.
Plz let me how can we stop the adapter ,so that no more IDOCs are received .
We are looking for some API (IDPI framework) if available.
Locking the RFC users is not an acceptable soln here.
Hope to get some info soon.
Regards
Dhanya

Hi Dhanya,
there is a way on PI side alone
for IDOC 2 steps needed:
1st: Determine all the IDoc metadata that is involved in your communication in IDX2 (basically all idoc types that the sending system sends) then deleted it all
2nd: Determine the IDoc port of the sending system in IDX1 (it should be an RFC destination pointing to the sending system) then Disable or delete that port
On runtime a validation of the loaded idoc metadata happens on PI and the sending side (experienced this on ERP6 & ERP5, not sure on lower versions >4.5), if the sending system determines that there is an inconsistency between its idoc structure against the idoc structure loaded in PI the idoc will be stuck in trfc queue (SM58) having error something like table EDI*** conflicts. In our case when you disable the IDoc port in IDX1 and there is no idoc metadata in IDX2 when the sending system tries to send idoc PI will try to fetch the idoc metadata but it won't be successful because the IDX1 port is disabled already.
for HTTP, you can try to disable service /sap/xi/adapter_plain in SICF but please consider the resending of the message should be handled also on the sending side.
hope this helps

Stop invoice idoc with Zero lines

Hi all,
I need assistance on how I can stop the ouptut to create an invoic idoc with zero value.
Else
as we create workflows for invoice creation. that means we use workflow as soon as the PGI(post goods issue) is done we creare invoice - Can we build a functionality to stop it from creating invoice if the PGI done and the items/ lines with zero value not passed.
Thanks in advance
Jasmeet

Making the bold assumption that you use an outbound IDoc process code that invokes function module IDOC_OUTPUT_INVOIC, you have the user exit LVEDF001 available. This is a standard exit that can be activated and maintained via CMOD.
The first function exit in LVEDF001 is EXIT_SAPLVEDF_001. It contains a call to the include program ZXEDFU01. Therein you can add code that will delete invoice line items having zero quantity or net value from the communication structure DTVBDPR before the IDoc is created.
Regards,
Ken

Stop generating the IDOC, soap-xi-idoc

Dear SDN,
I have a interface SOAP(HTTP) -> XI -> R/3.
In this interface, 3rd party sending 4 fields and are getting updated in R/3.
Now, I need to change in this interface.
There are 4 fields in sender side and one field is like (PersonNumber)primary field. while updating this fields, I have to check whather the primary field is exist in R/3 then only update remaining fields else do not update the record/IDOC in R/3.
And we are using XSLT mapping.
The intension of the chage in interface is when the PersonNumber doesnot exist then do not generate the IDOC. whenever the PersonNumber is not there the system is generating the IDOC details with status 51.
So I need to stop generating IDOC when the PersonNumber is not there in R/3 system .
In this scenario, how can I procede further.
Please need your help and help me.
Thanks
Bala Prasad

Hi,
In XI you can stop an interface (without generating error) only in receiver determination.
In your case you can use receiver determination condition which checks if PersonNumber is coming blank etc. If blank then choose a non existing receiver and choose the option "Terminate Message Processing without any error"
In case if you have any complaex condition then you will have to go for enhanced receiver determination.
Let me know in case you need any further help.
Regards,
Anurag Mahendru.

Stopping idocs coming into XI production system

Hi Frndz,
We have XI production for the maintenance purpose, we have to stop only the idocs coming into and going out of the SAPXI system.
So how to stop the idocs coming into the system keeping SAPXI system running(other traffic related FILE, JDBC, JMS etc....) ???
<removed by moderator>
Regards
Sai Ganesh
Edited by: Mike Pokraka on Jul 24, 2008 1:17 PM

Hi,
Adding to the Michal post, You can also do
If you dont want to Push the Idocs to XI in future means, In R/3 We20--Change the Port( create dummy file port and assign it)
If u want to post the Idocs to Xi means follow Michal Reply
And also In reverse case while posting the Idocs to R/3, change the RFC Destination name in IDoc Receiver Adapter.The messages will be stay in XI in Errored state
Afterwards if u want to push the Idocs From XI to R/3 means, change the RFC Destination name in Idoc receiver adapter and say Restart.
Regards
Seshagiri

IDOCs stopped getting created for FB01 transaction

Hey Guys,
I m facing a strange problem, the idocs for message type FIDCC2 was getting creating for transaction FB01, FBR1, FPG1. But from sometime it has stopped creating the IDOCs. I have not chnaged anything in the system. Not sure why this has caused so.
Please help me out on this ?? also I need to change the segment data for the same, Please share me a user exit where i can incorporate this???
Raj

Hi,
There is no error as such, we did the config for the FIDCC2 message type Basic type FIDCCP02 and whenever we post a FI document and IDOC was getting created.
Now just earlier, it suddenly stop generating IDOCs we did n't make any change to the system. The source and sestination system is up and running. Not sure what caused this...
Raj

JDBC to IDOC Error

Hi Guys
On my Scenario Jdbc to Idoc (Asynch) I am using FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01
as a Receiver Interface, now when testing on the sxmb_moni I get two flags the Black and While and the Red the one the is Back and While shows that the Sender is my JDBC Adapter which is right
but now the Red flag show that the Sender is IDoc(FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01) is also Sender of which I used it as a Receiver Interface, I dont know how to stop this IDoc Adapter not to send but to receiver.
Basical my scenario is meant to create an IDoc but is is not doing it when going to TCode WE02/WE05 I get message : "No IDocs selected"
Thanks
Yonela

Hi
I don't have any conditions, to Send and Receive, by the way I went to TCode IDX5 my Outbnd is right but Inbound thats where I get the below error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error
I have done these:
SM59- To Create RFC Destinations
WE21- To Create IDoc Ports
SALE- To Create Logical System
WE20- To Create Partner Profiles
IDX1- Port Maintenance in IDoc Adapter
IDX2- Metadata Overview for IDoc
On the ID I created the the IDoc Receiver:
RFC Destinatin: IDOC_RECEIVER
Interface Version: SAP Release 4.0 or Higher
Port: SAPPI1
SAP Release: 701
What could be the problem
Thanks,
Yonela

Custom status message in ALE HRMD_A IDOC

Hi,
We are using HRMD_A idoc for integrating two SAP systems. We want a custom check to be included in the ALE outbound processing, where for example if a field of an infotype is some value then we want to stop the IDOC from being transferred to the target SAP system. IDOC should stop with a custom error message in the status record. Is this possible using any of the user exits?
Thanks in advance,
Shravan

Requirement looks bit strange to me, if at all the IDoc is not needed to be sent for error message then why to Generate them, just filter out creation of IDocs by setting the Filters in Distribution model.
For your requirements you may want to take a look at Badi HRALE00OUTBOUND_IDOC.
Regards
Shital

Idoc Scenario from SAP to SAP via PI 7.1o

Q: Two idocs will process from SAP to SAP via SAP-PI 7.1o and generated together.
Requirement :
Sync
2 IDOCs – as we explained our design will require two IDOCs. The first IDOC will be developed by a Z code and the second IDOC is generated by 100% Standard SAP BAPIs and 2 IDOCs send them to PI. Both IDOCs will be generated together by process code in sap and must be moved to PI and later to the receiver client together(SAP). The process can only be 100% completed when both IDOCs will be processed with success in the receiver side. Any one of the IDOC among 2 idoc's failed all the process should stop.
i think that is not possible , PI will not be able to stop successfull IDOC If another IDOC get fails .
Please give me approaches if any chance .
Thanks, Sanakr

Hi Bhavani,
You can use BPM with correlation to achieve this scenario:
Demonstration of ccBPM Scenario: SAP PI 7.1
**************** - BPM Scenario using Fork and correlation
Regards,
Suman

Not generating IDOC for payment Advice to Vendors

Hi,
IDOC was getting generated before one month but now SAP system has stopped generating IDOC for vendor Payment advice. This problem is with all the vendors.
After execution of t-c-ode F110, payment document is successfully created, but IDOC is not geenerated. There is no log about "IDOC not getting generated"
Checked Table REGUH, IDOC number is displayed as 0000000000000.
This was happening perfectly one month back.
There is no change in Vendor master data, IDOC number range is available.
There is no posting of IDOC in table DFKKTHP and checked Report REREMITADV for which there is no data.
Waiting for your valuable responses.
Regards
veleyudham

Hi,
First check certain customization:-
(1) FBZP setup for payment method at country level. Whether IDOC generation program is assigned or not.
(2) Then check the variant of RFFOEDI1 in the printout tab of F110. Is the selection creteria OK?
(3) Check the partner profile in WE20 for the bank.
Then run the program RFFOEDI1 in SE38 for your payment run and check the output.
You can also get this program debugged from you ABAPer to have root cause analysis.
Regards,
Gaurav

Stop PO idoc

Similar Messages

Maybe you are looking for