NEED BAPI FOR SALES CONTRACT CREATION AND EXTRACTION FOR Trans- PA41& PA43

Hi All,
I need the BAPI for T-code PA41 and PA43 for sales contract.
i would like to extract all the contract details for Contract data contains Table VEDA. And need to create contract.
Any body please help me out...
Please give me code if any one have how to do mapping ..
Thank you,
Vishnu.

Hi Vichu,
Please search on SCN.
Regards
Abhii

Similar Messages

Regarding bapis for sales order creation and modification

Hi,
I am trying to create a syncbo for sales order creation, modification and display. The bapis that I am using are
1.BAPI_SALESORDER_GETLIST
2.BAPISDORDER_GETDETAILEDLIST
3.BAPI_SALESORDER_CREATEFROMDATA1
4. BAPI_SALESORDER_CHANGE
Am I using the correct bapis. When I tried to create a syncbo it gave the following errors
BAPISDORDER_GETDETAILEDLIST does not have RETURN parameter in export or tables parameter
RETURN parameter in Create BAPI Wrapper should refer to structure BAPIRET2
RETURN parameter in GetList BAPI Wrapper should refer to structure BAPIRET2
GetDetail BAPI Wrapper does not have RETURN parameter in export or tables parameter
No Export parameter referring to header structure exists in GetDetail BAPI Wrapper
No Import parameter referring to header structure exists in Create BAPI Wrapper
No Import parameter referring to header structure exists in Modify BAPI Wrapper
No Import parameter referring to a field of header structure exists in GetDetail BAPI Wrapper
No Export parameter referring to a field of header structure exists in Create BAPI Wrapper
No Tables parameter referring to item structure exists in Create BAPI Wrapper
No Tables parameter referring to item structure exists in Modify BAPI Wrapper
I am informed that the above bapis are standard bapis.
I am not sure as to why I am getting the errors.
Does the syncbo require the bapi's to be in a specific format.
What would be the header and item structures for sales order bapis
Regards
Raja Sekhar

Hi Raja,
ya , for creating Sync BOs ,our BAPI wrappers must satisfy certain conditions..
just go through this link.
u can use the standard BAPIs of SALES Order in ur Custom BAPI Wrapper
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/what_is_a_bapi_wrapper.html
the RETURN must be of type BAPIRET2..
Regards
Kishor Gopinathan

LSMW-BAPI Method sales contract creation

Hi,
I have a requirement to create sales contract through batch input or bapi method or idoc .
Please let me know if there are any existing applicable methods for it.
with regards,
Bharath

Business object BUS2034, method CreateFromData.
There is no ALE interface delivered for this BAPI in our system but you might generate with transaction BDBG.
Regards Jack

Automatic TO Creation and Confirm for the 321 Mvt type

Hello Experts,
Like to know the customisation invovlved for automatic TO creation and confirmation for the 321 movement type in which QM is activated.
I have already activated in OMKZ as below
1.Automatic TO for 321 mvt ytpe
2.TO item to be confirmed immediately
3.Propose confirmation
Table T333 -AUTTA
          T333-SQUIT &
          T333-VQUIT is activated.
Please let me know any other settings to be performed
Regards
Krishna

Hello Experts,
I am trying to create the Automatic TO and TO confirmation for the mvt type 321.
I made the below settings
I have activated in OMKZ as below
1.Automatic TO for 321 mvt ytpe   -"A"
2.TO item to be confirmed immediately - tick mark
3.Propose confirmation   - tick mark
Table T333 -AUTTA
T333-SQUIT &
T333-VQUIT is activated.
I have activated in OMKX as below
Table T321-TBFKZ Immediate TO Creation with "A"
T321-TAFKZ TR creation with "X"
After doing the settings i am not able to see the Posting change number in the Material document created for the mvt type 321.
Please let me know how to create the Posting chnage notice for the material document and how to convert the Posting change notice to automatic TO and confirmation.
Thanks & Regards
Krishna
Edited by: Hariharan krishna on May 25, 2011 8:01 AM

Function Module or BAPI for Sales price calculation and Pricing worklist

Hi Retail experts,
We frequently change purchase conditions, but not that frequently for cases like perishables, so sales price calculations needs to be done each time. This means pricing worklist generation and release is done often and then sales price recalculation is done each time article wise and for various organization level.
We have 15000 articles for which purcahse conditions changes, it is impossible to generate and release pricing worklist and do sales price calculation for each article
So solution may be to find a FM/BAPI for the following transactions and automate them.
Do you know FM/BAPI for VKP5/VKBP or VKP6, WVN0, WVN1 transactions.
Regards
Bob

HI Madhu,
Thanks for the reply,
I am looking for BAPI or FM which will check all pricing condition types( like MRP of the Material(table A304), discounts(A800,A802,A803,A804) for that customer and Tax) and give me the value(KONP-KBETR).
I can only pass Customer, material, quantity etc.. so that BAPI or FM has do all standred checks/ validation and give the
KONP-KBETR for all condition types like MRP, discounts, Tax. we are developing the custom program for sales order creation so we require the all this before saving the sales order.
Regards,
Nagesh
Edited by: nageshdb4u on Mar 5, 2011 12:05 PM

Quotation Creation and Billing for Service Orders--node details needed

Hi ,
I need to work on node "Quotation Creation and Billing for Service Orders" ....I see lot of integration with SD and FICO . Can any one give details about integrations required and what is done in this node ....
Regards
NPB

There are different steps to be done for that.
1. Create DIP Profile in ODP1 & check the consistency in ODP2 - DIP will be used to bill the customer based on resource (labor & material) usage. Creation of DIP profile has been discussed many times in this forum. Please check.
2. Assign the Quotation document type & Billing type used in DIP profile to your sales area - Your document type should be assigned to your sales organisation, distribution channel & division combination.

Need code for Sales order creation in oops using xi as integration server

Need code for Sales order creation in oops using xi as integration server.

hi rocky,
could you pls give a bit explanation on what you are expecting.
regards,
Pavan

Using BAPIs for sales contracts

Hi,
I'm having this situation that I have to upload sales contracts into SAP from flat files. We planned to use BAPIs for this purpose. Is it a good option. Can anyone suggest better ideas. If BAPI is a good option, has anyone used standard BAPIs for sales contracts updation in SAP System. If yes, can you guide me through the process.

Hi,
You can start off with a program with:
Get the filename of the convert file
IMPORT /SAPDMC/LSMEMORY FROM MEMORY ID '/SAPDMC/LSMW'.
V_PROJECT = /SAPDMC/LSMEMORY-PROJECT. " Project
V_SUBPROJ = /SAPDMC/LSMEMORY-SUBPROJ. " Subproject
V_OBJECT = /SAPDMC/LSMEMORY-OBJECT. " Object
IF V_PROJECT IS INITIAL.
    V_PROJECT = 'XXXX_LOC'.
ENDIF.
IF V_SUBPROJ IS INITIAL.
    V_SUBPROJ = 'SD'.
ENDIF.
IF V_OBJECT IS INITIAL.
    V_OBJECT = 'XXXX_VA41'.
ENDIF.
Function will return path of converted file by LSMW object
CALL FUNCTION '/SAPDMC/LSM_FILE_INFO_GET'
    EXPORTING
      PROJECT           = V_PROJECT " /sapdmc/lsmemory-project
      SUBPROJ           = V_SUBPROJ " /sapdmc/lsmemory-subproj
      OBJECT            = V_OBJECT   " /sapdmc/lsmemory-object
      X_ONLY_USED_FILES = 'X'
    IMPORTING
      FILE_CONV         = V_DSNAME   " Path of converted file
    EXCEPTIONS
      NO_SUCH_OBJECT    = 1
      OTHERS            = 2.
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
I am not much of an LSMW expert so wont be able to comment much.
regards
Aveek

Function module which uses both BAPI's for sales order create and change

Please name the function module which uses both BAPI's for sales order create and change.
BAPI_SALESORDER_CREATEFORMDAT2
BAPI_SALESORDERCHANGE

Yup.
you must write a piece of code for this.
with if else condition.first check if SO is exsist than use second FM to change it else create new SO from first FM.
logic somethig like this.
Amit.

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Partner function for sales contract

Hi
I have to extract Sales related data from SAP R/3 to BW.
Facing issue if someone just changes partner function for Sales contract as they are not captured in any of the standard extractors.
If there is change in partner function for Sales order then it gets captured in 11 vascl but if its for contract then it doesnt get capture.
Any solution ?
Regards,
monika

Hi ! Ivy
I guess there is a option.
Try this out. Use the menu path IMG> Sales & Distribution> Sales> Lists> Set updating of partner index
In the resulting screen, click on 'New Entries' make entries 0 - for sales orders and 4 - for contracts as transaction group. Under the column 'partner function' ener the partner function for which you want the report and save your entries.
Now when you go for executing your report, click on the push button 'Partner functions' ( Say in VA05) , you will have the option for selecting the new partner functions , select and execute your report.
Provide your feedback.
Regards,
PATHIK

Automatic TO creation and confirmation for a Material document

Hi Dear All,
i am new to MM andWM.
I have to customization for auto transfer orders and confirmations for material documents what ever created with 101 movement type in Inventory Management. I have down configuration like below.
SPRO->Logistics Execution->Warehouse Management->Activities->Transfers-> Set Up Autom. TO Creation for TRs / Posting Change Notices
Double click on control data tab
Hear for my warehouse I given input like   Auto TO = 1,
                                                                         AddId = select check box.
And in Assign control tab for 101 movement type I have given input like below.
Automatic TO = 1.
TO item can be confirmed immed. = tick checkbox
Propose Confirmation = tick checkbox.
Foreground/Backgrnd = D.
After creating of Material document I am executing report RLAUTA10 in SE38.When I execute this report system showing message like TO processing finished: TR total:   17, TO created:    0, Errors:   17.
If I check header details of transfer requirements in LB03, i am not seeing Tick Mark in Auto TO Creation field.
Can any one tell me what the mistake i have down or if i need to do any further configuration. Please help me regarding this concern?
Thanks in Advance..

Dear Steve,
Thanks a lot for giving reply with what I need to do, but I am unable to see result.
I have down configuration like below even though system not processing Auto TO creation. Can you explain me if I have down any mistake below.
Click on Assign button,
Press on New entries
WhN = 900
Reference Movement Type = 101
Movement indicator = B
Movement type for Whse Mgmt = 101
TR create Transfer Requirement = X
Immed.TO Creation
Mail confirmation for background processing = 01.
GR date = 2

How to trigger an Idoc from Sales order creation and change

We are trying to trigger Idoc from sales order creation and change we have done following setting mentioned below:
Follow the below steps:
1. Go to NACE transaction
2. Select V1 application and select OUTPUT TYPES
3. Select the required output type and double click on Processing routines.
4. Enter Medium as DISTRIBUTION ALE, Program as RSNASTED and Routine as ALE_PROCESSING.
5. Save it.
message type ORDERSP in the distribution model (BD64).
Follow the below steps to configure the condition records:
1. Go to NACE
2. Select V1 application and select CONDITION RECORDS
3. Select the requred output type and click on Condition records
4. Selection screen will be displayed.
5. Go for execution. In that screen enter the selection criteria. For eg Condition record is based on Sales document type. Then
Sales doc type = OR
Funt = SP
Partner = blank. It means there is no restriction on partner numbers.
Medium = A
date/time = 4
Lan = EN.
Note: partner is left blank means, the sales order of type OR can be send to all partners.
6. Save it.
We also done ALE configuration.
We are facing problem that from VA02 "No output has been selected for printing Message no. V1102"
Kindly suggest the solution.
Regards,
Sharad Dixit

Hi ,
Please check the total error description and diagnosis as below :
InVa02 enter SO go to extras->output->Header->edit.You can find a table with all the triggered output types. Choose the output type BA00 with medium Distribution ALE and go for 'Processing log'. It will show you the error description.
Please paste the diagnosis .
Thanks and Regards,
P.Bharadwaj

IDoc Configuration for Production Order Creation and Change

Hi All,
Please Help me out for IDoc Configuration for Production Order Creation and Change
I have found the IDoc for Production Order
Messgae Type : LOIPRO and IDoc type : LOIPRO01
Actually my requirment is to send the (LOIPRO01 )IDoc from SAP R/3 to XI system ,when ever the Production Order Created and Changed,
I have done following Configurations:
1. RFC Destination created for XI system
2. PORT was created for XI
3. Partner profile created WE20 and LOIPRO01 IDoc is added in OutBound Perameter.
I need to know how to do the followning.
1. How do i configure the outbound Production order idocs when Production Order is created or changed.
2. in NACE (Output control) which is the Application for Production Order.
3. How can I set IDoc as output Type for Production Order Creation.
Thanks in advance
Dhanabal T

Hi Michal,
I know that it is the old thread but still want to get clarified from you out of curiosity.
Unlike other IDOC, i actiavated change pointers for LOIPRO
1.message and idoc type is linked
2.function module , message type , idoc type is linked
function module used is CLOI_MASTERIDOC_CREATE_LOIPRO
3.BD64, distribution model is created and distributed
4. port and partner profile is in place.
5. IDOC is not getting generated after creating the process order.
do we need to activate the change documents for the message type in BD52,
if yes can you please provide the object types for the same.
or i am missing something else. please guide me in this regards.
Thanks in advance for your time.
S.Janagar

BC SETS creation and usage for sap mm point of view

Hi All,
Need Information About BC SETS creation and usage from sap mm point of view.
Thanks in advance for sap mm forum guys.
Regards.
Parameshwar.

Hi,
Customizing settings can be collected by processes into Business Configuration Sets (BC Sets). BC Sets make Customizing more transparent by documenting and analyzing the Customizing settings. They can also be used for a group rollout, where the customizing settings are bundled by the group headquarters and passed on in a structured way to its subsidiaries.
BC Sets are provided by SAP for selected industry sectors, and customers can also create their own.
When a BC Set is created, values and combinations of values are copied from the original Customizing tables into the BC Set and can be copied into in the tables, views and view clusters in the customer system. The BC Sets are always transported into the customer system in which Customizing is performed.
Advantages of using BC Sets:
1.     Efficient group rollout.
2.     Industry sector systems are easier to create and maintain.
3.     Customizing can be performed at a business level.
4.     Change Management is quicker and safer.
5.     Upgrade is simpler.
To create BC sets follow the below step:
Choose Tools ® Customizing ® Business Configuration Sets® Maintenance in the SAP
menu, or enter the transaction code SCPR3 in the command field.
Choose Bus.Conf.Set ® Create.

NEED BAPI FOR SALES CONTRACT CREATION AND EXTRACTION FOR Trans- PA41& PA43

Similar Messages

Maybe you are looking for