BTE type B not triggere

Hi ,
I have used a BTE of type B (Business Object). I have copied the sample function module and created a product and assigned the same to product in P/S function modules and also check active flag. I have posted a document. But my function module is not triggered. Do I need to do any more customizing. Please advice.
Thanks & Regards,
Kalyan.

Vishnu,
Thanks for the info. I have already done the steps described by you. My problem is resolved now.As it is a Business object type BTE it will not be invoked if event is not triggered.In my case business object event is not triggered,because of this BTE is not invoked.Thanks for the response.
Cheers,
Kalyan.

Similar Messages

Output Type is not triggering

Hi,
We have created routine in output determination(VOFM) to trigger the output type (for IDoc) when ever Sales Order is created and we have configured correctly. Access Sequence containes KOMKBV1, KOMPBV1, etc.
When I checked in development system, I am getting values in KOMKBV1, KOMPBV1, etc and it is serving my purpose,
But when i tested same in quality system, KOMPBV1 structure is not getting values and this is not serving my purpose ( i.e output type is not triggering) .
Could any one please suggest me why it is happening.
Regards,
Aditya.

There is no problem with Access sequence
Below are the fields for the accesss sequence.
Sales document type KOMKBV1     AUART
Sales organization      KOMKBV1     VKORG
Distribution channel     KOMKBV1     VTWEG
Division                        KOMKBV1     SPART
Customer group 5        KOMKBV1     KVGR5
Plant                             KOMPBV1     WERKS
The same is working fine in Developemnt but not in quality.
I went to debugging mode while creating a sales order in both systems for checking where exactly KOMPBV1 is getting cleared.
I could find in
SAPMV45A
MV45AF0B_BELEG_BEARBEITEN_ENDE
FORM BELEG_BEARBEITEN_ENDE
Call function messaging
When the program is going in this..... the value for KOMPBV1 is getting cleared in Quality but the same this is working fine in Development...
Hope this coulld help you in understanding the problem better.
Edited by: Aditya K Ghanaria on Nov 30, 2010 4:13 PM

Custom output type is not triggering automatically

Hi Experts,
We have created a custom output type for Delivery idoc processing.
it is working fine for all ship to patrys.
but from last 2 months onwards we are facing problem for one ship to party.
output type is not triggering automatically but for rest of ship to party's it is triggering automatically.
we have maintained conditions and also selected trigger immediately.
earlier it was working fine, but from last 2 months onwards we are facing this problem.
Thanks
Sai

Hi,
Goto the Delivery document and in the Output screen check the Determine analysis for output.
There it will clearly show what is missing .
Please check that and revert back if you need more clarification.
regards,
santosh

IDOC message type LOIPLO not triggering

Hi Friends
Our client want to send firmed planned orders to External system through outbound IDOC LOIPLO
So we are using MF50 to firm the planned orders.
The idoc message type LOIPLO is not triggering.
How to trigger IDOC message type LOIPLO . What are the settings we have to do.
Regards,
Srihari.M

dear friend,
Message Type : LOIPLO
Basic Type : LOIPLO01
You need not create any custom IDOC type as we are having a standard IDOC type available within SAP, but you need to write a custom function module to read the data from the IDOC segments and then call the below BAPI to post the Planned Order.
Check the input parameters of BAPI and gothrough the documentation of the Basic Type in WE60 transactions, whether all the necessary input parameters of the BAPI are covered in the standard IDOC type, if not then we need to customize the standard basic type to meet the requirements.
Bapi which needs to be used is BAPI_PLANNEDORDER_CREATE
good luck!

Message type is not triggered in SAP when PO copied from eSHOP

Hi,
We are creating PO in eShop and sending to SAP.
POs are correctly getting copied from eShop to SAP.No issues.
We have set condition record for Message type to trigger in SAP for those POs as EDI Medium.
No message is getting triggering in SAP.
Whether it is standard one ? or any further enhancement required ? If so please suggest the BAPI.
Thanks

Hi Dhina
What is the application eSHOP?.
for example
In SAP SRM - Technical scenario - Extended Classic.
Purchase orders were created in SRM -EBP and replica of Purchase Orders were replicated to ECC system. In the above scenario messages are created in SRM not ECC.
The PO messages are out puted to vendor from SRM itself.
So please clarify what is meant by eShop. so others can help you further ..
Muthu

BTE for F110 Not triggered

Hello Gurus,
I have a BTE for FI ZPFRFI_PROCESS_00001120 which is a copy of BTE SAMPLE_PROCESS_00001120 . This BTE is also configured properly and activated.But when i run F110 transaction this BTE is not trigerred .if anyone have come across this issue please reply.

Hi,
What is ur exact requirement.
I had a requirement to send a mail to vendor while paying through F110.
I used BTE 00002040 in Infosystem (processes) for tcode F110.
U can chk out the same BTE by copying sample FM in Z..FM.
u need to create entry in Customer Enhancement.
Plz chk out if dont know the procedure let me know.
Regards,
Ankur.

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

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.

posted this question in ERP forum.

BTE 00001030 - Dunning form - OPEN_FI_PERFORM_00001030_P not triggering

Hi,
I am using BTE 1030 for replacing the assigned form in customizing settings with a 'Z' or customer specific one at runtime. (determine dunning form)
Although, I placed a Break-point (hardcoded) in my 'Z' function module, properly registered as a customer product, etc...
I debugged the complete process using Background debugging and the function module responsible for holding the 'OPEN_FI_PERFORM_00001030_P' .
As per the SAP standard functionality this can be used to replace or overwrite the form assigned to the DUNNING in SPRO with customer form.
When I run my DUN (F150) it doesn't encounter the break-point nor it goes to the standard 'OPEN_FI' statement '00001030'.
Also logically while printing dunning notices it system encounters 'PRINT_DUNNING_NOTICE' which must be triggered and it contains the 'GET_DUNNING_CUSTOMIZING' function module. The 'OPEN_FI' lies in this function module. But none of the above is triggering while 'Background debugging'.
Till now I am unable to resolve this issue.
Kindly, suggest me a better approach.
Best regards,
Harsh Dave
Edited by: Harsh Dave on Apr 1, 2009 2:08 PM

Hello,
Yes, that might be the case.
But, In in my case the BTE 00001030 shows (Process interfaces) - DUNNING - Determine form
As per SAP documentation, this is useful for replacing the dunning form determined during customization settings with 'custom' dunning form at runtime.
In fact, when I debug the 'print_dunning_notices', the table 'APCUSTAB' - for customer enhancement products on customer level is empty.
Hence, my BTE is not triggering, although I have registered my BTE as a customer.
Do you have any suggestions?
Best regards,
Harsh Dave

Output type is not getting triggered for ship to party in shippment output

Hi,
we have maintained output determination procedure for shipments. It was working fine.
We have just added new condition table to access sequence, and maintained the condition records also for condition type ZABC. I have checked in NACE, Application V7, I am able to find the condition type. checked in VV73, condition records displayed. But in VT02N/VT03N, we are unable to get print for the output type.
Why this is happening? we are able to see the procedure, condition type, access sequence, condition records in place ...why condition type ZABC is not getting triggered in the shipment output.
Please advise and let me know if you need more details....thanks in advance.
Thanks,
SS

Hi Noel,
Thanks for your time and reply.
We have output determination procedure for shipments, condition type ZABC, Access sequence ZABC, Condition tables 550,600,650,700 already maintained. output is working fine.we have a new requirement and created new condition table 700 with the fields" Ship to party and transportation planing point "(Condition table 700 ). we assigned the condition table 700 to access sequence ZABC. Condition type ZABC already placed in Output determination procedure.
We test the output, new condition record is not triggering in the output, even in output determination analysis also, we are unable to see the record 700 for the condition type ZABC. we are not sure what is the reason for the condition table that is not picking up ? Why condition type ZABC with condition record 700 not visible in output determination analysis.
I have checked condition records, output determination procedure. Please advise and let me know you need more details.
Thanks,
SS

Delivery Output type newly created not triggering

Hi,
I have created 2 new output types i;e 1 for returns Order and one when we save the Delivery order. This i have copied the standard output type (BA00 & LD00).
so now in returns order the output type i want to trigger automatically and print. But it is not happening. In VV11 i have defined for this condition as Print immediately and in customizing also i have maintained for sales organisation. But it is NOT triggering automatically when i save the return order. If i manually go and add this output then its working. So can you please tell me what needs to be done to trigger automatically.
Secondly for Delivery i have 2 output i;e when i save the delivery without picking and all in VL01N, it should trigger 1 output and second is when i do the picking and PGI in VL02N. Both should trigger automatically.Now both my output is triggered only when i do PGI in VL02n i;e VL01N output is not triggered.
Please help how can i do that.

Hi,
Go to T-code NACE
Application area : V2-Shipping
Now select the condition records and select your new output types.
Take the key combination defined by you Viz. Sales org/Delivery Type (for example
Enter Medium as '1'
Date/Time as '4'
Press the communication Tab and Tick Print immediatley and release after output Check Box.
Also maintain the output device as LOCL
I hope this will help you
Br,
Tushar

BTE 1830 not triggered during F110 proposal run

Hi,
I am implementing 1830 (PAYMENT PROGRAM: Edit Group) to trigger at the time of proposal run in F110. But it's not triggering at the proposal run in F110.
I have assigned 1830 custom function module to BTE 1830 FIBF > Setting > Process Modules > Of a Customer.
Let me know how to troubleshoot this issue.
Thanks,
Ron.

I think you are on the right track.
I figured out the process myself.
In my case I assigned the custom FM to the BTE process 1830 like you did,
and tried to test it in a different Dev client.
But the assignment is stored in a Customizing transport which should be copied to the other Dev client by SCC1.
Long version short: did you check in your testing client if the assignment is visible in FIBF transaction?
Jeroen

Message type EDI is not triggering for outbound deliveries

Hello,
When ever the shipment status is completed message type EDI is triggered for the outbound delivery.
However, in spite of the shipment completion the DESADV EDI message is not created in the outbound delivery.
So, i request you to help me in this issue.
Regards,
Anil

Hi,
1st please check the partner porfile for whom it is sent ( Eg -- Ship to party) using T.code WE20 in partner type ku, look for the customer for whom it is sent.
Check for the message type wheter it is add in outbound parameteres.
Finally check the varaint of shipment whether the required output is maintained in the shipment varaint and also make sure that condition record is maintained for the output.
You find some solution with this.
Regards
vk

Output type should not be triggered when error in invoice

Dear Experts,
I have this issue.
Whenever there is an error in the document, the output type should NOT be triggered.
But in my case, in spite of the error "Pricing error in item 0001"the output is getting triggered.
This is a Billing Document.VF03.
In NACE, it is linked to RSNASTED-->EDI_PROCESSING form routine.
i need your help in identifying, where should be looking for this check.
check: when error in document->do not post idoc via the output type.
where will i be able to find this check.
Please guide.
Regs,
SuryaD.

FORM KOBEV_907.
*{   INSERT         D94K915917                                        1
* Declaration for Constants
constants : lc_kschl type char4 value 'ZNTP', " Message type
            lc_h type char1 value 'H',        " CREATE TRANS. TYPE
            lc_v type char1 value 'V'.        " CHANGE TRANS. TYPE
IF komkbv3-trtyp EQ lc_h.        " CREATE
IF komt1-kschl <> lc_kschl.
*   Check o/p type ZNTP in the newly proposed o/ps in table NNAST
    READ TABLE nnast WITH KEY kschl = lc_kschl.
    IF sy-subrc EQ 0.
      sy-subrc = 4.
      EXIT.
    ENDIF.
ENDIF.
sy-subrc = 4.
CHECK : KOMKBV3-UVALL CA ' C'.
CHECK : KOMKBV3-UVPRS CA ' C'.
CHECK : KOMKBV3-UVALS CA ' C'.
CHECK : KOMKBV3-RELIK EQ SPACE.
CHECK : KOMKBV3-RFBSK EQ 'C'.
sy-subrc = 0.
ELSEIF komkbv3-trtyp EQ lc_v.    " CHANGE
IF komt1-kschl <> lc_kschl.
* Check o/p type ZNTP in existing o/ps in table xnast and NNAST
    READ TABLE xnast WITH KEY kschl = lc_kschl.
    IF sy-subrc EQ 0.
      sy-subrc = 4.
      EXIT.
    ENDIF.
    READ TABLE nnast WITH KEY kschl = lc_kschl.
    IF sy-subrc EQ 0.
      sy-subrc = 4.
      EXIT.
    ENDIF.
ENDIF.
    sy-subrc = 4.
    CHECK : KOMKBV3-UVALL CA ' C'.
    CHECK : KOMKBV3-UVPRS CA ' C'.
    CHECK : KOMKBV3-UVALS CA ' C'.
    CHECK : KOMKBV3-RELIK EQ SPACE.
    CHECK : KOMKBV3-RFBSK EQ 'C'.
    sy-subrc = 0.
ENDIF.
*}   INSERT
ENDFORM.
the above code is what i see in RV61B907

Change pointer triggers for one order type but not for other with LOIPRO

Hi all,
We have old production order type ZP01 since last 3 years. Idoc LOIPRO are triggered properly. Now we introduced new production order type ZP02, but idocs are not triggereing for these prod. orders. They both are production orders with different order types but same message type LOIPRO
I noticed that change pointers are not getting written to CDHDR and CDPOS for this new order type. For old order type they are getting written to CDHDR/CDPOS. Does any one know where is the issue in config.
Currently BD52 contains following entries for LOIPRO
ORDER-AFKO-AUFNR
ORDER-AFKO-KEY.
Thanks in advance

Anyone with an idea.
The project went live by using RCCLORD or RCCLTRAN, but still the same orders keep triggering. How do we restrict the already processed production orders.

BTE type B not triggere

Similar Messages

Maybe you are looking for