Release Purchase Contract Programmatically

Hi Forum,
Is it possible to release a Purchase contract programmatically like the purchase order and the purchase requisition?
BAPI_PO_RELEASE does the job for Purchase Orders
BAPI_REQUISITION_RELEASE_GEN does it for Purchase Requisition
What does it for contracts?
Even a normal funcion module that is not RFC enabled is also okay. Any leads will be helpful.
Cheers,
Praveen

try to read your data with FM 'bapi_contract_getdetail'
maybe you can "dig" in the source code where your conditions are stored
regards
Jörg

Similar Messages

BAPI for Release Purchase Contracts

Hi Experts,
I have an ECC with a Workflow for approve Purchase Contracts, ok!!
I have too an External Program for approve this contracts, but I don´t know a BAPI or FM for export this requisitions to the External Program.
I know that for PO and PR exist BAPI's, but I did not found for the aprove Purchase Contracts.
Could you help me?
Regards,
Ariel Prebianca
Edited by: Rob Burbank on Sep 16, 2010 2:22 PM
Edited by: Ariel Prebianca on Sep 16, 2010 10:38 PM

Hi
The BAPI which you found for purchase orders works for Purchasing contracts also.
Please test.
Regards
Sachin

I want to create purchase Contract through workflow

Hi All,
I am working on Purchase contract through workflow. In that I am using business object BUS2014,
But in this business BUS2014, there is no event called create, So I take copy of business object BUS2014 to ZBUS2014.And I craeted event create & method end_date for checking the end date of contract.
The problem is, When I am using for t-code ME31k for release, If i am going to check t-code SWEL the event is not trigger on for release.
My requirement is when the contract is going to over then before 10 days the workflow event is trigger and give the remainder to creator & the vendor. And also same thing before 5 days it will give the 2nd remainder.
Please help me out regarding this.
Thanks & Regards,
Pankaj Sinha.
Edited by: Pankaj Sinha09 on May 11, 2009 10:07 AM

Hi there Sebastian,
You will need this 'extra Action' and QuickTime Pro...
http://www.apple.com/downloads/macosx/automator/quicktimecompressionactionsandwo rkflow.html
Regards
Ric

Purchase contract print preview is displaying items with DEL_IND='X'

Hi,
We are using SRM Server 5.5 and have a situation described below
A purchasing contract is created with, for example, 2 items with status as 'Held' . In change mode, the one item is deleted and the purchasing contract is Released.
When the button 'Output Preview' is pressed, the system displays the print preview with both the irems although one item is deleted.
I am trying to find SAP notes for this but I didn't find any relavent note.
I found one note for not displaying 'Inactive' status items however not found anything for excluding deleted items from print preview.
Appreciate your inputs on this.
Thanks and Regards,
Sambhaji Chawale

Thanks Georg for your inputs.
Yes, you are correct we are using custom developed smart form and not SAP Standard. We will be updating the smartform for adding the condition of u201Cselect items with deletion indicator=u2019Blanku2019.
However we are interested in the standard solution that SAP has provided to cover this. I don't see this condition in SAP standard smart form so this must have been covered through some program code.
Does anybody have idea on this.
Thanks and Regards,
Sambhaji Chawale

How to users from releasing a contract that they have created

Hi,
can someone tell me how tp stop users from releasing a contract that they have created and or changed. It should be released by a different user.
I've been doing some investigation, and it looks as if function module EXIT_SAPLEBND_002 (SAP Enhancement M06E0004) might be the User-Exit that I may need. Does anyone know if this is correct?
John

Hi,
You posted your query to wrong forum, should be posted to MM forum.
Anyway probably your users have the authority of transaction code ME35K (Release) and authority object M_EINK_FRG (Release Code and Group (Purchasing)) to be able release contract that they created.
Regards

How to copy custom fields in purchasing contract

Dear all, we have added to the standard field in the purchase contract position two custom fields.
These two fields (in value) are not taken when the user create a new contract by copying from another.
Are there some exit or BADI functions that allows to copy also custom ields into corresponding destination fields whitout modify the standard code ?
In customizing it seams there are aoly rulse for copy position texts.
Regards,
Riccardo Galli - Hera group.

Hi
Try to check the BADIs ME_PROCESS_OUT_CUST or ME_PROCESS_PO_CUST or the enanchement M06E0005, perhaps u can do something in the routines triggered as soon as the document is saved.
Max

Report for released purchase order

Hai guru's
this is second time but i did't get any good replay please consider this, i want any standard report for released purchase order,means(i released two backdated po today next day i verify the report ME2n,those po are not display, the system take only document date not released date, now i am using CDHDR through this i got the report. but it is big process, so once check this and send your valuable solution.
Prasad

Hi Krishna,
You could use Me2N with the dynamic selection coupled with normal selection screen.
In Dynamic selection(3rd icon in screen).....you can select for which company code, release indicator as released....and save it as default variant.
hope this should solve your query
Sk.

Release Value Contract Report

Hi,
As we can get individual customer released value contract amount through T Code VA43 and report Via T code Z_XX_SD_059 for mass customers which is usually not giving the correct amount of released from value contract. The report which is extracted via T code Z_XX_SD_059 normally not reconciled with the end result of T Code VA43.So, Is there any other T code for getting correct release value contract report for multiple customers? Please share if anyone knows.
Regards| Adnan Mahmood

Hi,
tcode Z is an in house development. Check with an abaper why there are differences with respect to VA43.
Regards,
JM

Error release purchase order using transaction code me29n

i have warning error this purchasing document number cannot be released.
while i enter me29n t code.why?
then how to release purchase order using me29n t code?
can anyone answer this two questions.

hi
i have warning error this purchasing document number cannot be released. while i enter me29n t code.why?
is the release strategy is triggred for the po ?? check thisin P order in me23n ,in header level check release strategy tab ,
then how to release purchase order using me29n t code? can anyone answer this two questions.
just go to me29n >release strategy tab here just click on the release button in front of the release code

Distribution of purchase contracts from SRM4.0 to ERP 2004

Hello all,
Any body has experience in distributing Purchase contract from SRM to R/3.
i have activated BADIs
BBP_DETERMINE_LOGSYS;BBP_CTR_BE_CREATE in SRM and BBP_CTR in R/3.
Right now i can create contracts in EBP,but i unable to transfer them to backend.
Until now i have followed the documentation stategic sourcing configuration guide.
Please give your valuble information to distribute service contracts.
Thanking you,
Mahesh Madasu.

Hi Mahesh,
If you are using classic scenario then try these:
Go to Table: BBP_DOCUMENT_TAB. Check whether your contract no.
Then go to T. Code: WE20 in Backend system.
Check for the Partner TYPE of you backend system in Partner profiile.
Go to classification TAB. And check the partner status is Activate or not. The status should be 'A'. Check the inbound Parameter BLAORD is present or not.
Then go to YOur SRM system and go to WE20 and activate the partner status by setting the parameter to 'A'. Then redo the processes.
This may help you.
Regards,
Charles

SD Customer Contract and MM Purchase Contract

Good day
I need to know if anyone has a solution on forming a relationship between these documents, and be able to report at item level for example Item x bought at $10 in the Purchase contract and sold at $15 in the Sales Contract. We need to form such a relationship between these contracts so we can report and compare line items.
Regards,
Iggy

I had similar requirement and used Purchase Order Header field 'Collective No' EKKO-SUBMI and put the Contract number in there. Then I used BADI ME_PROCESS_PO_CUST to do the budget check. I configured a new Contract Doc type and New PO Document type (with field selection requiring entry for EKKO-SUBMI) to provide more control. You will also want to create a custom report that lists the run rate/burn of the contract.
Other considerations
1) When the check fails, do you want error or warning ? we programmed it to be changeable via a ztable entry.
2) do you want to do any date checking of the PO header date(s) and the Contract validity date ?
3) do you want to check / verfiy the Purchasing organization of the Contract vs the PO ?
Sorry its late !

Z Report of Transaction ME28.(Release Purchase Order)

Dear all,
               I want to make Z Report for the Transaction ME28 (Release Purchase Order).
I am facing problem of GUI status in my Z Report. Actually Report is not displaying like ME28.
and all the menu and function keys are also not coming properly.
So, pls suggest me good solution.
Thanks & Regards,
Sandip Sonar.

I am attaching a copy of ME28. Please give it to your ABAP consultant.
He should be able to do the needful:
REPORT RM06EF00 NO STANDARD PAGE HEADING MESSAGE-ID ME.
       Anzeigen Einkaufsbelege zur Belegnummer                       *
Tabellen                                                            *
INCLUDE FM06LTO1.
INCLUDE FM06LCFR.
**table added t16fc - SAPBY     6 Feb 98
TABLES: T16FG, T16FS, T16FV, T16FE, RM06B, T160B, T16FC.
DATA: BEGIN OF XEKPO OCCURS 100.
        INCLUDE STRUCTURE EKPO.
DATA: END OF XEKPO.
*- Interne Tabelle der Zustände -
DATA: BEGIN OF ZUS OCCURS 10.
        INCLUDE STRUCTURE T16FV.
DATA: END OF ZUS.
DATA: BEGIN OF ZUSKEY,
         MANDT LIKE EKKO-MANDT,
         FRGGR LIKE EKKO-FRGGR,
         FRGSX LIKE EKKO-FRGSX,
      END OF ZUSKEY.
Parameter und Select-Options                                        *
PARAMETERS:     P_FRGCO LIKE T16FC-FRGCO OBLIGATORY.
SELECT-OPTIONS: S_FRGGR FOR EKKO-FRGGR.
PARAMETERS:     P_FRGSE LIKE RM06A-P_FRGSE DEFAULT 'X',
                P_FRGRS LIKE RM06A-P_FRGRS,
                P_FRGVO LIKE RM06A-P_FRGVO DEFAULT 'X',
set default to 'X' to show items as well - SAPBY
                P_MITPOS AS CHECKBOX DEFAULT 'X',
set default to 'DEFAULT' - SAPBY
                LISTU LIKE T160O-LISTU DEFAULT 'DEFAULT'.
SELECT-OPTIONS: S_BSTYP FOR EKKO-BSTYP,
                S_EKORG FOR EKKO-EKORG,
                S_EBELN FOR EKKO-EBELN MATCHCODE OBJECT MEKK
                                       MEMORY ID BES,
                S_BSART FOR EKKO-BSART,
                S_EKGRP FOR EKKO-EKGRP,
                S_LIFNR FOR EKKO-LIFNR MATCHCODE OBJECT KRED,
                S_RESWK FOR EKKO-RESWK,
                S_BEDAT FOR EKKO-BEDAT.
Hilfsfelder                                                         *
INCLUDE FM06LCEK.
DATA: XFRG1 LIKE EKKO-FRGZU,
      XFRG2 LIKE EKKO-FRGZU.
DATA: XSELKB LIKE EKKO-BSTYP,
      XSELKK LIKE EKKO-BSTYP,
      XSELKL LIKE EKKO-BSTYP,
      XSELKA LIKE EKKO-BSTYP.
FIELD-SYMBOLS: .
DATA: HFDPOS LIKE SY-FDPOS.
**workflow line added for workflow
DATA : LAST_USER_COMMAND LIKE SY-UCOMM.
Intitialisierung                                                    *
INITIALIZATION.
PERFORM ANFORDERUNGSBILD(SAPFM06L) USING XSELKB XSELKK
                                           XSELKL XSELKA.
lines 67, 70 and 73 commented out -SAPBY
**listu = t160b-listu.
S_BSTYP-SIGN = 'I'.
S_BSTYP-OPTION = 'EQ'.
**if xselkb ne space.
S_BSTYP-LOW = 'F'.
APPEND S_BSTYP.
**endif.
IF XSELKK NE SPACE.
    S_BSTYP-LOW = 'K'.
    APPEND S_BSTYP.
ENDIF.
IF XSELKL NE SPACE.
    S_BSTYP-LOW = 'L'.
    APPEND S_BSTYP.
ENDIF.
IF XSELKA NE SPACE.
    S_BSTYP-LOW = 'A'.
    APPEND S_BSTYP.
ENDIF.
next two lines added to default the release code
IMPORT T16FC-FRGCO FROM MEMORY.
get parameter id 'ZRC' field t16fc-frgco.
P_FRGCO = T16FC-FRGCO.
Seketionsbild                                                       *
AT SELECTION-SCREEN ON LISTU.
PERFORM LISTUMFANG(SAPFM06L) USING LISTU.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FRGCO.
CALL FUNCTION 'HELP_VALUES_FRGAB'
       EXPORTING
            I_FRGOT = '2'
       IMPORTING
            E_FRGAB = P_FRGCO
       EXCEPTIONS
            OTHERS = 1.
AT SELECTION-SCREEN.
CALL FUNCTION 'ME_REL_CHECK_MANY'
       EXPORTING
            I_FRGOT = '2'
            I_FRGCO = P_FRGCO
       TABLES
            T_FRGGR = S_FRGGR
            T_T16FV = ZUS.
Beginn der Selektion                                                *
START-OF-SELECTION.
NOT_FOUND = 'X'.
SET PF-STATUS 'FREI'.
SET TITLEBAR '001' WITH P_FRGCO.
PERFORM FRG_INIT(SAPFM06L) USING P_FRGCO P_MITPOS.
*- Lesen Belegköpfe -
SELECT * FROM EKKO APPENDING TABLE XEKKO
                     FOR ALL ENTRIES IN ZUS
                     WHERE FRGRL EQ 'X'
                       AND FRGGR EQ ZUS-FRGGR
                       AND FRGSX EQ ZUS-FRGSX
                       AND EBELN IN S_EBELN
                       AND BSTYP IN S_BSTYP
                       AND EKORG IN S_EKORG
                       AND LIFNR IN S_LIFNR
                       AND RESWK IN S_RESWK
                       AND BEDAT IN S_BEDAT
                       AND BSART IN S_BSART
                       AND EKGRP IN S_EKGRP
                       AND LOEKZ EQ SPACE.
IF P_FRGRS NE SPACE.
    SELECT * FROM EKKO APPENDING TABLE XEKKO
                       FOR ALL ENTRIES IN ZUS
                       WHERE FRGRL EQ SPACE
                         AND FRGGR EQ ZUS-FRGGR
                         AND FRGSX EQ ZUS-FRGSX
                         AND EBELN IN S_EBELN
                         AND BSTYP IN S_BSTYP
                         AND EKORG IN S_EKORG
                         AND LIFNR IN S_LIFNR
                         AND RESWK IN S_RESWK
                         AND BEDAT IN S_BEDAT
                         AND BSART IN S_BSART
                         AND EKGRP IN S_EKGRP
                         AND LOEKZ EQ SPACE.
ENDIF.
SORT XEKKO.
*- Prüfen Freigabevoraussetzungen -
LOOP AT XEKKO.
    MOVE-CORRESPONDING XEKKO TO ZUSKEY.
    READ TABLE ZUS WITH KEY ZUSKEY BINARY SEARCH.
    CHECK SY-SUBRC EQ 0.
    XFRG1 = ZUS+9(8).
    XFRG2 = XEKKO-FRGZU.
    TRANSLATE XFRG2 USING 'X +'.
    OVERLAY XFRG1 WITH XFRG2 ONLY '+'.
    SEARCH XFRG1 FOR 'X'.
*---- Keine Freigabezuständigkeit -
    IF SY-SUBRC NE 0.
      DELETE XEKKO.
    ELSE.
*---- Freigabestelle merken -
      HFDPOS = SY-FDPOS.
      ASSIGN XFRG2+SY-FDPOS(1) TO .
*---- Freigabe bereits erfolgt -
      IF P_FRGRS EQ SPACE AND
          EQ SPACE.
        DELETE XEKKO.
      ELSE.
*---- Freigabe noch nicht erfolgt -
        IF P_FRGSE EQ SPACE AND
            NE SPACE.
          DELETE XEKKO.
        ELSE.
*---- Freigabevoraussetzung fehlt -
          IF XFRG1 CA '+' AND
             P_FRGVO NE SPACE.
            DELETE XEKKO.
          ELSE.
            EKKO = XEKKO.
            PERFORM FRG_FEKKO_AUFBAUEN(SAPFM06L) USING HFDPOS.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDIF.
ENDLOOP.
SORT XEKKO.
*- Lesen Belegpositionen -
IF P_MITPOS NE SPACE.
    SELECT * FROM EKPO APPENDING TABLE XEKPO
                       FOR ALL ENTRIES IN XEKKO
                       WHERE EBELN EQ XEKKO-EBELN.
ENDIF.
*- Ausgabe -
LOOP AT XEKKO.
    EKKO = XEKKO.
    PERFORM EKKO_ANSCHRIFT(SAPFM06L).
    PERFORM EKKO_AUSGABE(SAPFM06L).
    IF P_MITPOS NE SPACE.
      LOOP AT XEKPO WHERE EBELN EQ EKKO-EBELN.
        EKPO = XEKPO.
        PERFORM FC_ME_READ_HISTORY(SAPFM06L).
        PERFORM EKPO_AUSGABE(SAPFM06L).
      ENDLOOP.
    ENDIF.
ENDLOOP.
Ende der Selektion                                                  *
END-OF-SELECTION.
IF NOT_FOUND NE SPACE.
    MESSAGE S260.
    IF SY-CALLD NE SPACE.
      LEAVE.
    ELSE.
      LEAVE TO TRANSACTION SY-TCODE.
    ENDIF.
ENDIF.
WRITE: /(81) SY-ULINE.
OK-Code-Eingabe                                                     *
AT USER-COMMAND.
**workflow inserted 6 Feb 98 by SAPBY
    PERFORM WORKFLOW_AT_USER_COMMAND.
INS GSB 18/02/2004 - check user approving is not user that create
PO
if sy-ucomm = 'FRGU' or sy-ucomm = 'FRGS'.
loop at xekko.
if xekko-ERNAM = sy-uname.
     CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'
       EXPORTING
         TITEL              = 'Error'
TEXTLINE1 = 'As the creator of this pruchase order you cannot approve it
as well !'
    leave program.
endif.
endloop.
endif.
PERFORM USER_COMMAND(SAPFM06L).
Seitenueberschrift                                                  *
TOP-OF-PAGE.
PERFORM TOP(SAPFM06L).
TOP-OF-PAGE DURING LINE-SELECTION.
PERFORM TOP(SAPFM06L).
**& form workflow_at_user_command
TEXT
---> p1 text
<-- p2 text
FORM WORKFLOW_AT_USER_COMMAND.
IF LAST_USER_COMMAND IS INITIAL.
    LAST_USER_COMMAND = SY-UCOMM.
ENDIF.
IF SY-UCOMM EQ 'ZURU'.
     PERFORM TRIGGER_WORKFLOW.
ENDIF.
CASE SY-UCOMM.
    WHEN 'BU'.
      IF P_MITPOS EQ 'X'.
        CHECK LAST_USER_COMMAND <> 'FRGR'.
        PERFORM TRIGGER_WORKFLOW.
      ELSE.
        CHECK LAST_USER_COMMAND = 'FRGS'.
        PERFORM TRIGGER_WORKFLOW.
      ENDIF.
    WHEN 'FRGU'.
      PERFORM TRIGGER_WORKFLOW.
ENDCASE.
LAST_USER_COMMAND = SY-UCOMM.
ENDFORM.
**& form TRIGGER_WORKFLOW.
TEXT
---> p1 text
<-- p2 text
FORM TRIGGER_WORKFLOW.
DATA : BEGIN OF ZEKKO OCCURS 20.
          INCLUDE STRUCTURE ZEKKO.
DATA : END OF ZEKKO.
DATA : BEGIN OF YEKKO OCCURS 20.
          INCLUDE STRUCTURE ZEKKO.
DATA : END OF YEKKO.
DATA : WFBAN LIKE EKKO-EBELN,
       WFERN LIKE EKKO-ERNAM.
CLEAR : WFBAN, WFERN.
MOVE-CORRESPONDING XEKKO TO YEKKO.
CONCATENATE YEKKO-FRGZU 'X' INTO YEKKO-FRGZU.
APPEND YEKKO.
MOVE-CORRESPONDING XEKKO TO ZEKKO.
*XEKKO-KZ = 'F'.
APPEND ZEKKO.
SELECT SINGLE KOKRS KOSTL
     INTO (EKKN-KOKRS, EKKN-KOSTL)
     FROM EKKN
     WHERE EBELN = XEKKO-EBELN
     AND EBELP   = '00010'.
if sy-subrc <> 0.                  " Cost centres not mandatory at XXX
exit.
endif.
CALL FUNCTION 'Z_ME_REL_EVENT_EKKO'
     EXPORTING
          I_CALL_UPDKZ = 'F'
          I_WFBAN      = EKKO-EBELN
          I_FRGCO      = T16FC-FRGCO
          I_ERNAM      = SY-UNAME
          I_UCOMM      = SY-UCOMM
     TABLES
          I_EKKO_NEW   = YEKKO
          I_EKKO_OLD   = ZEKKO.
ENDFORM.

Tables for Purchase contract Tax pricing

Hi ,
     I want to display purchase contract detail in the standard layout.
For Displaying pricing we need the Document condition number of the contract.
Normally in Purchase order pricing document number is in EKKO table and field name is KNUMV.
In same procedure i search for Contract pricing but am not able to find the pricing document number table and the pricing table.
Please guide me how can we pick the pricing values from purchase contract.
what is the tables for purchase contract Tax pricing ?
Regards,
Madhan - Chennai .

hii,
     it is
               KONH                                    Conditions header
                KONP                                    Conditions items
                KONV                                    Procedure ( billing doc or sales order)
                KOND
                      VEDA                                     Contract data
regards,
Shweta

Smartforms on Purschase Order and Purchasing Contracts in SRM system

Hi Friends,
Can anyone provide sample example of smartforms on Purchase Order and Purchsing Contracts in SRM system?
It is great, if you send me valuable material to create smartforms on PO and Purchase Contracts in SRM system.
Thanks in Adv.
BABA

Hello BABA,
Try this link. Hope this helps.
[Re: Creating SRM PO with Smartforms BBP_PO;
Please discuss this issues in SRM- General forum for better replies.
Cheers,
Suvendu

How to use BLAREL03 standard iDOC to upload Purchasing contract to SAP

Hello
Guru's
Thanks in advance for your time.
we ae planning to upload purchasing contract details to SAP using BLAREL03 standard idoc.
can any one give me step step procedure to follow.
i am new to IDOC's i need little bit detail. give me with function modules names to upload.
In any way can we test it quickly,by creating text file with mandatory fields on the idoc and upload it.
we just worried about like contract start date,end date,(how it is handling while uploading) the fields which are on tree view of idoc, are not there,if we look at flat file structure of idoc.

Hello
Guru's
Thanks in advance for your time.
we ae planning to upload purchasing contract details to SAP using BLAREL03 standard idoc.
can any one give me step step procedure to follow.
i am new to IDOC's i need little bit detail. give me with function modules names to upload.
In any way can we test it quickly,by creating text file with mandatory fields on the idoc and upload it.
we just worried about like contract start date,end date,(how it is handling while uploading) the fields which are on tree view of idoc, are not there,if we look at flat file structure of idoc.

Release Purchase Contract Programmatically

Similar Messages

Maybe you are looking for