Automatic creation of BP relationship while BP is created

We are implementing CRM SALES and using Portal as the user interface.
The requirement is that a Sales Rep should be able to see only the
accounts and contacts (which is nothing but Business partners in the
GUI side) that they have created when they list account using "My
Accounts" in Portal. We are configuring Portal in a such a way that
"My Accoounts" is the only view available for Sales Rep portal.
I have tested and found that if a relationship category of "is the
reponsible employee" is created from the sales rep to the Account OR
Contact then that account or contact will be displayed in the "My
Accounts" or "My Contact"view in Portal.
But requesting a Sales Rep to create the relationship for every
Account and Contact that they create in CRM will NOT be accpetable at
all.
Hence I am looking for an option with which a relationship of "is the
Responsible Employee" can be created automatically when an account or
contact is created by the Sales Rep.
Please let me know your ideas.

Hi Rajadurai,
In the BADI - BUPA_FURTHER_CHECKS implement the method - CHECK_CENTRAL.
The following code could serve your purpose:
IF IV_ACTIVITY eq '01'. "Check if it is for creation
CALL FUNCTION 'BUPR_RELATIONSHIP_CREATE'
   EXPORTING
    IV_PARTNER_1 = IV_PARTNER
    IV_PARTNER_2 = LV_createdby "BP no of the creator
    IV_RELATIONSHIP = 'BUR011' "Code for emp. resp
    IV_DATE_FROM = SY-DATLO
    IV_DATE_TO = '99991231'.
endif.

Similar Messages

Set automatically closed indicator in PR while contract/agreement created

Hi experts,
Is there any possibilities that we can set automatically closed indicator in PR while contract/agreement created?
Normally, PR closed indicator is set when PO created refer to the PR.
Is there any IMG configuration to utilize this matter?
Thanks
MD

Hi,
You can try this using the Userexit in PR.So once the RFQ or Agreement is created for the PR then the ststus will be changed.
Check this user exit.MEREQ001 Customers' Own Data in Purchase Requisition
Regards,
Raj

Configure the automatic creation of accounting document while billing

Hi,
Could you telme where to find the customization where you configure such that
triggering of automatic creation of accounting document takes place during billing itself.
Regards
anil.

Hi Anil,
In VOFA Document type in General contrlo is related to Accounting Document.If it is blank the system Automatically pics RV as accounting Document.
If posting Block is Ticked then Automatic posting will not happens.
You need to pass to Accounting in VF02 and release for accounting(Green Flag)
Regards,
Reddyy

Automatic creation of settlement rule while creating sales order

Hi Friends,
Can any one help me how to create settlement rule automatically while creating sales order i.e saving sales order. Is there any function module or any badi which can be used.. please suggest.
thanks
bobby

Hi,
Here is the solution , First Create a sustitution by going into OPSN Transaction , only user exit say 'U902'
and write the form routine in Program named 'ZRGGBS000'
The code is below ,
*&      Form U902
   Automatic Generation of Settlement Rule For WBS and Company 4180
FORM u902.
Exit For Automatic Settlement Rule Creation for WBS Billing elements
IF sy-tcode = 'CJ20N' or sy-tcode = 'CJ01' or sy-tcode = 'CJ02'.
    DATA   lv_proj TYPE ps_pspid.
    lv_proj = proj-pspid.
    EXPORT lv_proj TO MEMORY ID 'PSPID'.
Calling YGPS_CJB1EXEC Program For Creating Settlement Rule
    SUBMIT ygps_cjb1exec AND RETURN.
ENDIF.
ENDFORM.                                                    "u902
*& Program YGPS_CJB1EXEC
PROGRAM ygps_cjb1exec.
   Automatic Generation of Settlement Rule For WBS and Company 4180
Called From Exit For Automatic Settlement Rule Creation for WBS Billing elements
DATA: bdcdata_wa TYPE bdcdata,
      bdcdata_tab TYPE TABLE OF bdcdata,
      itab TYPE TABLE OF bdcmsgcoll.
DATA :lv_currm LIKE bkpf-monat,
      lv_curry LIKE bkpf-gjahr,
      lv_prevm LIKE bkpf-monat,
      lv_prevy LIKE bkpf-gjahr,
      lv_proj TYPE ps_pspid,
      lv_mode TYPE c,
      lv_time TYPE sy-uzeit.
DATA :g_datfm            LIKE usr01-datfm,
      g_dd(2)            TYPE c,                         " Day
      g_mm(2)            TYPE c,                         " Month
      g_yyyy(4)          TYPE c,                         " Year
      g_sydatum(10)      TYPE c.
IMPORT lv_proj FROM MEMORY ID 'PSPID'.
lv_mode = 'N'.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKAZB'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'PRZB-VARIANT'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'PRZB-VARIANT'.
bdcdata_wa-fval = 'ZGPS0001'.
APPEND bdcdata_wa TO bdcdata_tab.
CALL FUNCTION 'GET_CURRENT_YEAR'
EXPORTING
    bukrs = '4180'
IMPORTING
    currm = lv_currm
    curry = lv_curry
    prevm = lv_prevm
    prevy = lv_prevy.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-FROM'.
bdcdata_wa-fval = lv_currm.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-GJAHR'.
bdcdata_wa-fval = lv_curry.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=VARC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'RKPSEL00'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'CN_PROJN-LOW'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_PROJN-LOW'.
bdcdata_wa-fval = lv_proj.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_PSPNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_NETNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_ACTVT-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_MATNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '/00'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=SAVE'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=VBAC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLSPO1'.
bdcdata_wa-dynpro   = '0100'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=YES'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKAZB'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-BATCH'.
bdcdata_wa-fval = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-TEST'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=RUN'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKABA'.
bdcdata_wa-dynpro   = '0210'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-JNAME'.
bdcdata_wa-fval = 'CJB1_EXEC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_SUBSCR'.
bdcdata_wa-fval = 'SAPLKABA'.
APPEND bdcdata_wa TO bdcdata_tab.
Extract the date format from the user settings
PERFORM f_get_dateformat CHANGING g_datfm.
Changing the current date format to User Profile Date Settings
PERFORM f_format_date USING   g_datfm
                              sy-datum+4(2)
                              sy-datum+6(2)
                              sy-datum+0(4)
                     CHANGING g_sydatum.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-STDAY'.
bdcdata_wa-fval = g_sydatum.
APPEND bdcdata_wa TO bdcdata_tab.
lv_time = sy-uzeit + 30.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-STTME'.
bdcdata_wa-fval = lv_time.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-PRIKZ'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=TAKE'.
APPEND bdcdata_wa TO bdcdata_tab.
Calling Transaction 'CJB1' for creating settlement rule
CALL TRANSACTION 'CJB1' USING bdcdata_tab MODE lv_mode .
IF sy-subrc = 0.
ENDIF.
*&      Form F_GET_DATEFORMAT
      This subroutine returns the date format in the user setttigs
     <--P_G_DATFM Date Format
FORM f_get_dateformat CHANGING p_g_datfm.                   "#EC *
SELECT SINGLE datfm FROM usr01 INTO p_g_datfm
WHERE bname = sy-uname.
ENDFORM.                    " F_GET_DATEFORMAT
*&      Form F_FORMAT_DATE
      This subroutine returns the date as per the user settings
     -->P_G_DATFM Date Format
     -->P_G_MM Month
     -->P_G_DD Day
     -->P_G_YYYY Year
     <--P_G_DATE Date
FORM f_format_date USING    p_g_datfm
                            p_g_mm
                            p_g_dd
                            p_g_yyyy
                   CHANGING p_g_date.                       "#EC *
CONSTANTS: c_dot VALUE '.',
             c_slash VALUE '/',
             c_dash VALUE '-',
             c_1 VALUE '1',
             c_2 VALUE '2',
             c_3 VALUE '3',
             c_4 VALUE '4',
             c_5 VALUE '5',
             c_6 VALUE '6'.
DATA: l_day(2),
        l_month(2).
l_day = p_g_dd.
l_month = p_g_mm.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = l_month
    IMPORTING
      output = l_month.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = l_day
    IMPORTING
      output = l_day.
CASE p_g_datfm.
    WHEN c_1.
      CONCATENATE l_day l_month p_g_yyyy INTO p_g_date
          SEPARATED BY c_dot.
    WHEN c_2.
      CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
       SEPARATED BY c_slash.
    WHEN c_3.
      CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
          SEPARATED BY c_dash.
    WHEN c_4.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_dot.
    WHEN c_5.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_slash.
    WHEN c_6.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_dash.
ENDCASE.
ENDFORM.                    " F_FORMAT_DATE
thanks
bobby

Automatic creation of BP relationship at the time of creation of BP

When a user creates a new account using BP transaction we need to create a 'Has the responsible employee' relationship automatically. If we try to create the same on save ( Using function BUPR_RELATIONSHIP_CREATE in BAdI PARTNER_UPDATE ) it doesn't work as the account would not have got created at the time of save. Hence we took a different approach of trying to create the relationship when the user clicks on 'Relationship' button ( in portal it is 'Relationship' tab ). We couldn't find a suitable BAdI which would contain the details of the recently created account as its import parameter. Is there any other approach we could use to solve this issue? Please let me know your ideas on the same.

Hi,
You can implement this functionality using the BDT.
--> in the PAI event, update the relationships in memory using function BUB_BUPA_RELATIONS_MODIFY.
For BDT use, take a look at the following thread:
Re: How do I update custom fields in a partner when I save the record?
Michael.

Automatic creation of an equipment using the serial number

Dear All,
I know that we can configure the automatic creation of an equipment while creating a serial number. I would like to know if some of you have details on how the creation is performed. In particular:
I saw on an other thread that the descirption, serial number are populated on the equipment from the material master data, but is there any possibility to classify the equipment with the classification assigned to the material master data ?
Thanks,
Kind regards,
Guillaume

Hi,
Try this link:http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e0244299-278d-2e10-4fac-e28fffb12588
James Prabaharan

Automatic creation of Material Master at the time raising the PO !!!

Hello All,
I am stuck in a scenario of our client which should be implemented (or mapped) in SAP.
Scenario: At the time of creating the PO (in there legacy system -in house developed) they can choose the items from the existing master data or/and they can also add a new item (which is not present in the master data records at the time of creating the PO).
Now as soon as the system realise that a new item is inserted into the PO, it will create that item record automatically in the backend (database) and the master data will be present from there on.
The items they are dealing with are all fashion accessories and they generate order on the following basis:
1. Demand of particular item in market.
2. List of items provided by the vendor.
3. Based on the requirement in there outlets.
So for them its very difficult to fix there master data records, as it can be changed daily or monthly as per the market conditions. At the same time every time they order, its almost around 100 different items (some time 80 of them are new) in a single PO so they cannot create 80 records manually each time.
These items are not consumable material so obviously they are maintaining the stock for them. They are also not going to use IS Retail.
I am not at all sure how can we map this particular practice in SAP, it would be really appreciated if any one could help me on this problem.
Please let me know if you need any other details from my side.

Hi,
As you have two different systems one in house developed and another SAP, and the PO creation part starts from Legasy system which creats the PO in SAP, you can do some development as per below
1: While Passing the details from legasy to SAP, use two columns in legasy one will contain the Material Code of ECC (for laready exist material ) and another for deescription of material.
2: In case material is new for which there is no material master in ECC pass only description from legasy systems.
3:While getting triggred from Legasy to ECC to create the PO, first check whehter all the material code exists or not in ECC.
4:If some material are not created (only description present) for those material first create the Material Code using BAPI 'BAPI_MATERIAL_SAVEDATA'.
5: Aftre creation of Material code create the PO using BAPI ' BAPI_PO_CREATE1'.
6:For the new created material , trnasfre the master record from ECC to Legasy systemso that next time user can see that material in your legasy system.
Regards,
Zafar

Automatic Creation of Service Order

Hi
What config settings do I need to maintain in order for servce orders to be generated automatically during the creation of disconnection documents.
I have created service objects in Work Management, but the service orders are not created.
Thanks

Hope you have mentioned the order type while maintaining the Service Object in OISC.
Regards,
Rajini.

Automatic creation of PO's from Requisitions

Hi
I'm trying to get a grasp of what's needed to automatically create approved PO's upon approval of a requisition.
There seems to be two ways to do it, a release program under a Contract Agreement, or using workflow with a Global BPA.
Under either method, would you need to create a Contract Agreement or Global BPA for each and every supplier? Is there any easier way to achieve this?
Thanks

To automatically created Approved PO's you will need the following
1. To create Standard PO's a Requisition will have to use a Quotation. This quotation can be attached to an ASL to default while creating a req
The Workflow "PO Create Documents" should have automatic creation allowed set to yes
2. To create Releases a Blanket PO must be attached to an ASL . The Workflow "PO Create Documents" should have automatic creation allowed set to yes
Please let me know if you have any questions
Thanks
Navin

Automatic creation of po during goods receipt

Dear all,
po has not been created, but while receiving the material i want automatic generation of po. i have some knowledge about it but it is not working. Can some one send detailed information. with navigation details. Tips that are posted on the sdn is not working.
Regards

Hi
Pl Make sure you have done following settings for the Automatic Creation of PO during GR:
1) In SPRO ---> Enterprise Structure ---> Assignment -
> Material Management ---> Assign Std. Purchase Org. to your Plant...
2) In Material Master -
> Purchasing View -
> Pl. Check. Automatic PO check Box   and Maintain Purchasing Group....
3)Create your Vendor for oyur Company Code and Std. Pur. Org. combination and in that Vendor Master -> Purchasing Data View--- > Pl. Check Auto. PO Check Box...
4)For your Vendor -Material Master - Plant -Std. Pur. Org combination Maintain valid Info record...
5)In OLMB ---> Goods Receipt -
> Automatic Creation of PO ---> for the M.Type:101 pl. check Auto PO check Box
6) In OLMB ---> Movement types ---> Copy,Delete, Check M.Types ---> Choose the M.Type:101   and go into Details -
> Then goto allowed Fields for M.Types for M.Type:101 ---> there for the M.Type:101   make the field   LIFNR as a Mandatoty field...
If you have done the above settings properly...then in MIGO ---> Choose Transaction GR and referance as Others
and do the GR....Make sure you are doing GR with M.Type:101....and yougive the Vendor's name during   GR....
Now If you save the GR ...automatically PO will be created...
this you can see it by displaying the MIGO Document..
Reward if useful
Regards
S.baskaran

Automatic Creation of Settlement Rule for Maintenance Order

Hi,
While doing TECO for Maintenance Order, its asking for Settlement Rule. IF I click settlement rule, message is coming as Maintain Settlement Profile with options like With Default, Without Default & Cancel.
I have maintained the Cost center in Equipment Master. Also I maintained Cost Center as Default Settlement receiver.
Also I have gone through setting in Automatic Creation of Settlement Rule under Controlling Category.
But I couldnt understand that. Can you please tell what are the steps to be done?
Regards,
Maheswaran.

Hi,
Please check the indicatorsin Actual cost/cost sales and Valid recevivers in settlement profile.
If for cost center : 1 settlement optional is maintained in valid recevivers and also for order
and in actual cost/ cost sales: indicator to be settled in full is selected.
Also check Allocation structure too if you have assigned the valid allocation structure.
**check if you have assigned the valid settlement profile to order types.
*****Most important after doing all these settings you need to create new order. for same order you will not get the automatic settlement rule
Hope this helps.
Regards,
PMAddi

Automatic creation of TO from TR

Hi
While doing automatic creation of TO from TR through SE38 through the programme RLAUTA10 following error is getting thrown
"Processing type is not maintained for automatic TO creation
Message no. L3404"
Diagnosis
To process transfer requirements / posting changes during automatic transfer order creation, you require a processing type that is maintained in the Customizing appplication when you set the control for automatic TO creation.
Procedure
Maintain the processing type in the Customizing table specified above.
Pls help me how to resolve this

hi Kumar,
you have to maintain automatic creation of TO in backround for your im movement type in OMKZ.
also in backround you have to activate backround processing in OMKZ(it will go to SM36).There you have to give the job name and processing time(periodically,one time etc..)
regards
venkadesh

How to create automatic creation of BP from customer and vendor master data

Hi gurus,
can any one tell how to create automatic creation of BP from customer and vendor master data.
Please give me the steps.
Thanks
Sasikanth.

HI,
Goto SPRO\ Cross application components \ Master data synchronization \ Synchronization control.
Assign account groups of customer and vendors to respective BP grouping. This setting is enough to create BP in background while creating customer / vendor. But the fields groups are very much important, ensure mandatory fields should be sync.
rgds,
Srini

Stop Automatic Creation of Inspection Lot for a condition

Dear Gurus,
While Creating a Delivery through a Sales Order, Config is maintained such that "Inspection Lot" will be automatically Generated.
Now Business wants to Stop this Automatic Creation of Inspection Lot only for a Particular Delivery Type and for a particular mode of Transport.
Do we have any User Exits / BADIs to achieve this requirement.
Please let us know.
Thanks in advance.
Regards,
Vinay Mutt

Hi
To meet you above mentioned requirement you have to modify the program RQAAAS10 as per your logic both to create lot for Expired Material and to consider project stock or vendor stock as In standard SAP these stock are not considered.
regards
Manish

Automatic creation of maintenance order before expiry of warranty

Hi All,
I have a requirement to generate maintenance order automatically when a particular assets warranty is soon to expire.
I am aware of the option to get pop-up box while creating maintenance order if the equipment is under, but this wll not meet my requirement.
Could you please provide your comments.
-Vasanth

Hi,
you can go for general preventive maintenance plan creation. whatever your requirement is, you can create relevent task list, assign your strategy of maintenance for that asset after its warranty is over and so on up to a particular period, say 365 days.
Then create strategy plan (IP42) and schedule it in such a way that it generate its first call object by the end of warranty and keep on generating as per your requiremnts. schedule it (IP 10), and you will get call objects (notification or order) as per your requirements.
It is an standard SAP practice, hopw it will work for you, without any enhancements.
Regards,
Lucky.

Automatic creation of BP relationship while BP is created

Similar Messages

Maybe you are looking for