BBP_BS_GROUP_BE for new document type and number range

Hi gurus,
I am working on Classic scenario in SRM and currently have used the above BADI to use a different document type and number range when creating the PO in the backend system. It all works fine. The only thing is I noticed that the BE_DOC_TYPE field in the shopping cart is still reflected as 'EC' even though the PO created in ECC is for example EC1. My question: Is this standard SRM? If so, is it common to leave this field as it is or is it advisable for us to change the document type to EC1 as well? Also, is there any implication in standard SRM reporting and downstream processes that you are aware of?
Appreciate any advice on the above.
Cheers!
Sf

We have ended up having to populate the document type on a custom field or alternatively replace the existing one.

Similar Messages

Document Types and No range

Hi Gurus, i am new to SAP,
please guide me in
Configuring document types and number ranges for PR, RFQ, PO, Quantity Contract, Value Contract and Scheduling Agreements with release.
Thank is Advance
Kapil

You have to maintain No Ranges for PR at Materials Management->Purchasing->
Purchase Requisition->Define Number Ranges
Define number range interval
Choose type of number assignment (internal or external)
You maintain the associated number ranges in the step Define Number Ranges under "Purchasing".
SAP recommends that you accept the settings defined in the standard system. In this case, no action is required on your part.
<b>Document type</b>
Purchase Requisition->Define Document Types
Steps
1)Create new document types
2)Define the item interval
3)Allowed Item category.
4)Define allowed follow-on document types
5)Assign document types to a number range group
Similarly for all the processes you can maintain Number ranges and Document Types at IMG menu path at Purchasing.
Reward if helpful
Regards
Sanjay l

New Document Types and new Number Ranges

Hi,
Plz tell me How to configure New Document Types and new Number Ranges for Services and Asset Purchases.
How can i maintain Services with or without Master data.
Plz tell how much services are there and how to configure step by step

Hi
New document type can be configured in SPRO - SAP IMG- Material management - Purchasing - Purchase order - Define number rabges / define document types.
With out service master straightaway you can create the Service PO with account assigment.
AC03 - Create service master record.
ML10 - Model service specifications
Then Service conditions ML33 or ML39 or ML45
Create the PO and then do the service entry in ML81N
Regards,
Raman

Document type and No. range for non leading ledger

Hi Friends,
can anybody tell me about the document type and No. range I can take for the non leading ledger.
Regards

Ok Pankaj,
I am taking document types by copying it from the SAP standard document type and the No. range identical to the No. range assigned in the standard Doc. type. Is it ok
LA                9A
LB                 9B
LC                 9C
LD                 9D
LE                  9E
LF                  9F
LG                  9G
LH                  9H
LI                   9I
LJ                  9J
LK                 9K
LM                 9L
LN                 9M
LN                 9N
LO                 9O
LP                  9P
LQ                 9Q
LR                  9R
LR                  9S
LS                  9T
LT                  9U
LU                 9V
LV                9W

Could you check our source? (To determine the PR type and number range)

Hello.
We use SRM Server5.5 with Classic Scenario.
We will use the BADI BBP_SC_TRANSFER_BE to determine the PR type and number range according to your recommend.
We have two PR type in R/3.
1) KGPR
2) KTR1
As you know that shopping cart has no type. So we add customer field to mapping to R/3 PR type and this field has two values.
1)     PR01: mapping to KGPR
2)     PR02: mapping to KTR1
We will use the method GROUP_RQ to determine the PR type.
If customer field is PR01, PR type is determined KGPR
If customer field is PR002, PR type is determined KTR1.
To determine the PR number range, we will use the method GET_NUMBER_OR_RANGE.
If PR type is KGPR, Choose the No key 12
If PR type is KTR1, Choose the No key 16.
Configuration step:
1.     Maintain the PR number range in SRM.
No key: 12 (for KGPR) internal NR
No range: 2520000000 2529000000
No key: 16 (for KTR1) internal NR
No range: 2560000000 2569000000
2.     Maintain the PR number range in R/3
No key: 12 (for KGPR) Ext NR
No range: 2520000000 2529000000
No key: 16 (for KTR1) Ext NR
No range: 2560000000 2569000000
3.     Assign the PR number range to PR type in R/3
KGPR 12 (EXT)
KTR1 16 (EXT)
4.     Maintain the attribute in SRM
Document type in R/3
      Add KGPR and KTR1
We developed this logic, but its not working.
LOOP AT ct_proc_item INTO ls_proc_item Where is no date in ct_proc_item:
We can not find out the reason.
Could you check our source?
METHOD if_ex_bbp_sc_transfer_be~group_rq.
DATA:
       ls_proc_item           TYPE bbps_procurement,
       lv_number_int          TYPE bbp_item_no,
       ls_item                TYPE bbp_pds_transfer_item,
       lv_group_counter       TYPE numc5,
CONSTANTS:
      lc_on(1)               VALUE 'X'.
SORT ct_proc_item BY obj_to_gen.
CLEAR: lv_group_counter.
LOOP AT ct_proc_item INTO ls_proc_item
where obj_to_gen eq iv_object_to_generate.
get item data which includes customer fields
    MOVE ls_proc_item-preq_item TO lv_number_int. " convert
    READ TABLE it_item INTO ls_item WITH KEY number_int = lv_number_int.
    IF sy-subrc = 0.
      IF ls_item-pr_type EQ 'PR01'.
        ls_proc_item-doc_type = 'KGRP'.
      ELSEIF ls_item-pr_type EQ 'PR02'.
        ls_proc_item-doc_type = 'KTR1'.
      ENDIF. " lv_cust_field
      lv_group_counter = lv_group_counter + 1.   " increase counter
      ls_proc_item-group_1 = lv_group_counter.
      MODIFY ct_proc_item FROM ls_proc_item
             TRANSPORTING group_1.
    ENDIF. " sy-subrc
ENDLOOP.
cv_method_active = lc_on.
ENDMETHOD.
method IF_EX_BBP_SC_TRANSFER_BE~GET_NUMBER_OR_RANGE.
if is_item-pr_type = 'PR01'.
     CV_NUMBER_RANGE = '12'.
     CV_NUMBER = '2520000000'.
elseif is_item-pr_type = 'PR02'.
     CV_NUMBER_RANGE = '16'.
     CV_NUMBER = '2560000000'.
endif. " is_proc_item / is_item
Thank you
Best Regard
SH

Hi
Please find some suitable sample code, which might help you out.
method IF_EX_BBP_SC_TRANSFER_BE~GET_NUMBER_OR_RANGE .
* IV_OBJECT_TO_GENERATE
*   '1' Reservation
*   '2' Purchase Requsition (BANF)
*   '3' Purchase Order
*   '4' Customer Object
* 1. current item data are in structures
*    - IS_ITEM shopping cart item data including Customer Fields
*    - IS_PROC backend relevant item purchasing data
* 2. accounting data in tables
*    - IT_ACCOUNT all shopping cart account. data with Customer Fields
*    - IT_PROC_ACCOUNT backend relevant accounting data for current item
* - key criteria between this tables are
*    - it_proc_account-preq_item
*                     -serial_no (numc 2)
*    - guid from is_item
*    - it_account-p_guid
*                -accno(numc 4)
* A) example to use current item data + item customer fields
* if is_proc_item-DOC_TYPE = 'ABCD' AND
*     is_item-<field of CI_BBP_ITEM> = .
* set own number range
* CV_NUMBER_RANGE = .
** set own number
** .. ==> if initial SAP Standard with no.range will be processed
* CV_NUMBER = .
* endif. " is_proc_item / is_item
* B) example to use only proc_account no accounting customer fields
*data:
*     ls_proc_account   type bbp_bapipogna.
* loop at it_proc_account
*            into ls_proc_account.
*    if ls_proc_account-BUS_AREA = '9988'.
** set own number range
* CV_NUMBER_RANGE = .
** set own number
** .. ==> if initial SAP Standard with no.range will be processed
* CV_NUMBER = .
*     endif. " ls_proc_account
* endloop.
* C) example to use only accounting customer fields, no other accounting
*data:
*     ls_account        type bbp_pds_acc.
* loop at it_account
*            into ls_account
*            where p_guid = is_item-guid.
*    if ls_account-<field of CI_BBP_ACC> = .
** set own number range
* CV_NUMBER_RANGE = .
** set own number
** .. ==> if initial SAP Standard with no.range will be processed
* CV_NUMBER = .
*   endif. " ls_account
* endloop.
* D) example to use proc_account + customer fields for accounting
*data:
*     lv_serial_no      type bbp_bapipogna-serial_no, " sequence num 2
*     lv_acc_no         type bbp_pds_acc-acc_no,       " sequence num 4
*     ls_proc_account   type bbp_bapipogna,
*     ls_account        type bbp_pds_acc.
* loop at it_proc_account
*            into ls_proc_account.
*    move ls_proc_account-serial_no to lv_acc_no.
*    read table it_account
*         into ls_account
*         with key p_guid = is_item-guid
*                  acc_no = lv_acc_no.
*    if sy-subrc = 0.
**     if ls_account-<field of CI_BBP_ACC> = .
** set own number range
** CV_NUMBER_RANGE = .
** set own number
** .. ==> if initial SAP Standard with no.range will be processed
** CV_NUMBER = .
**      endif. " ls_account
*    endif. " sy-subrc
* endloop.
endmethod.
method IF_EX_BBP_SC_TRANSFER_BE~GROUP_RQ .
* 1. current item data are in structures
*    - IT_ITEM all shopping cart item data including Customer Fields
*    - IT_PROC_ITEM backend relevant item data of current log.system
*    key criteria between this tables are:
*    - IT_ITEM-NUMBER_INT (numc 10)
*    - IT_PROC_ITEM       (numc 5)
* 2. accounting data in tables
*    - IT_ACCOUNT all shopping cart account. data incl. Customer Fields
*    - IT_PROC_ACCOUNT backend relevant accounting data for current item
* - key criteria between this tables are
*    - it_proc_account-preq_item (numc 5)
*                     -serial_no (numc 2)
*    - is_item-guid
*             -number_int (numc 10)
*    - it_account-p_guid
*                -accno(numc 4)
constants:
      lc_on(1)               VALUE 'X'.
* A) example to use only proc_item with NO customer fields
*         group requisitions by backend document type
*data: lv_doc_type            TYPE esart,
*      ls_proc_item           type BBPS_PROCUREMENT,
*      lv_group_counter       type numc5.
*    clear lv_group_counter.
*    clear lv_doc_type.
*    SORT ct_proc_item BY obj_to_gen doc_type.
*    LOOP AT ct_proc_item
*            into ls_proc_item
*            WHERE obj_to_gen EQ iv_object_to_generate.
** new group criteria?
*      if lv_doc_type ne ls_proc_item-doc_type.     " backend doc.type
*        lv_group_counter = lv_group_counter + 1.   " increase counter
*        lv_doc_type      = ls_proc_item-doc_type.       " save criteria
*      endif.
*      ls_proc_item-group_1 = lv_group_counter.
*      modify ct_proc_item from ls_proc_item
*             transporting group_1.
*    ENDLOOP.
* B) example to use item customer fields
* data:
*      ls_proc_item           type BBPS_PROCUREMENT,
*      lv_cust_field          type <field of ci_bbp_item>.
*      lv_number_int          type BBP_ITEM_NO,
*      ls_item                type BBP_PDS_TRANSFER_ITEM.
*    clear lv_group_counter.
*    clear lv_cust_field .
*    SORT ct_proc_item BY obj_to_gen.
*    LOOP AT ct_proc_item
*            into ls_proc_item
*            WHERE obj_to_gen EQ iv_object_to_generate.
** get item data which includes customer fields
*      move ls_proc_item-preq_item to lv_number_int. " convert
*      read table it_item
*           into ls_item
*           with key number_int = lv_number_int.
*      if sy-subrc = 0.
**       new group criteria?
*        if lv_cust_field ne 'XYZ'.
*         lv_group_counter = lv_group_counter + 1.   " increase counter
*         lv_cust_field = ls_item-<field of ci_bbp_item>."save criteria
*        endif. " lv_cust_field
*        ls_proc_item-group_1 = lv_group_counter.
*        modify ct_proc_item from ls_proc_item
*               transporting group_1.
*      endif. " sy-subrc
*    ENDLOOP.
* C) example to use accounting data with customer fields
*            group requisitions by backend document type
*data: lv_doc_type            TYPE esart,
*      ls_proc_item           type BBPS_PROCUREMENT,
*      lt_account             type BBPT_PD_ACC,
*      ls_account             type bbp_pds_acc,
*      ls_item                type BBP_PDS_TRANSFER_ITEM,
*      lv_number_int          type BBP_ITEM_NO,
*      lv_account_flag        type c,
*      lv_group_counter       type numc5.
*    clear lv_group_counter.
*    clear lv_doc_type.
*    SORT ct_proc_item BY obj_to_gen doc_type.
*    lt_account[] = it_account[].
*    SORT lt_account BY p_guid acc_no.
*    LOOP AT ct_proc_item
*            into ls_proc_item
*            WHERE obj_to_gen EQ iv_object_to_generate.
** get accounting customer fields for this item
*    clear lv_account_flag.
** ..first get item guid
*    move ls_proc_item-preq_item to lv_number_int.
*    read table it_item
*         into ls_item
*         with key number_int = lv_number_int.
*    if sy-subrc = 0.
*      loop at lt_account
*           into ls_account
*           where p_guid = ls_item-guid.
*        if ls_account-<field of CI_BBP_ACC> = .
*           lv_account_flag = lc_on.
*        endif.
*      endloop.
*    endif. " sy-subrc it_item
** new group criteria?
*      if lv_doc_type ne ls_proc_item-doc_type OR     " backend doc.type
*         lv_account_flag = lc_on.                    " accounting
*        lv_group_counter = lv_group_counter + 1.   " increase counter
*        lv_doc_type      = ls_proc_item-doc_type.       " save criteria
*      endif.
*      ls_proc_item-group_1 = lv_group_counter.
*      modify ct_proc_item from ls_proc_item
*             transporting group_1.
*    ENDLOOP.
* !!!! set flag that BADI was processed
* .. ==> no SAP Standard grouping will be processed
    cv_method_active = lc_on.
endmethod.
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Internal order types and number ranges

We have two SAP instances and want to load Internal order types and number ranges and Internal orders from 4.6 to 4.5 version.
I need to determine if there is an overlap of number ranges for the internal order types used in 4.6 and 4.5
Could you please help me how to approach? Manually verifying each range in both system is a tedious job and very confusing as the numbers are too big.

Hi,
I can suggest one thing which seems to be worth trying. Involve one technical guy in downloading the number ranges as well the orders of the numbers used from both the system and compare it. Then compile them and upload it again.
Trust this helps much!
Cheers!

To create document type related number range

Dear Experts,
I want to maintain number range document typewise say ABC, XYZ, LMN.
For these document type i want to maintain internal numcer range.
Please suggest.
Thanks

Dear all,
Go to SAP customizing implementation guide--> cross application component-> Document management--> control data--
.> Define ducument type.
Select document type for which internal number range has to be assigned and click on Details
nuber range assignment should be '1'
Then select the Internal number range for which your are going to assign say 04/05/06/08 etc
Then come back
Go to SAP customizing implementation guide--> cross application component-> Document management--> control data--> Define number range for document number
here for assinged number maintain required number range.
Thanks

Problem while print preview purchase order for new document type

Dear Experts,
I have got the problem as below and need your helps.
I created a new purchasing document type and then created a new PO with this document type. PO was created successfully in the system. I added a message to print out PO with the followed parameters as NEU output type, 1.Print Out medium , VN partner function, dispatch time is 3 ( Send with application own transaction).
Then, I clicked Print Preview button on the ME23n screen, the error message bellowed was shown
"The combination of document type
and Purchasing organization is invalid.
please check the document and change it.
unable to print the form"
I really want to print the PO with new purchasing document type on the existed purchasing organization, Could you please help me identify the problem and solution for this issue?
Appreciate for your responses.
Thanks,
Tinh Vo Trung
Edited by: Tinh Vo Trung on Sep 23, 2011 7:43 AM

Dear All,
Many thanks for your responses.
Regarding to maintain the condition record in MN04, I already done for that but the problem was not resolved.
Could you please come with the other posible causes and solutions for this issue?
Dear Bijay Kumar Barik,
Please let me know why we check the new document type in Program, Routine and From of NEU output type?
p/s: I compared the version the program, FORM and routine of NEU output type and found that there is no the differences btw DEV server and QAs server. However, An PO created susscessfully in QAs server, but the error was happend in DEV server.
Could you please come with the other posible causes and solutions for this issue?
Thanks,
Tinh Vo Trung

Link for sales document type and PO/delivery number

Hi guys,
I have a PO number(EKPO-EBELN) and the delivery number for STO(LIKP-VBELN), how am i going to link this 2 to get the SALES document type(AUART)?
thanks a lot!

mark,
So this is really not possible to get the pricing condition using the BAPI_SALESORDER_SIMULATE since this bapi requires the sales document type?
it depends if your delivery wrt to Sales document which is VBAK-VBELN than you can use above FM.here your deliver is created from STO so now you have to use select quesy as i already suggested as vijay also.
you may want to do same.
Amit.

Same Document type, Different number ranges

All SAP Gurus,
I want to assign Different number based on movement types, but the problem is that both the number ranges (101 for purchase order and 122 return delivery to vendor) are having the same document type (WE).
Is it possible to assign different number ranges to them?
Please give ur valuable suggestions.
Regards

In Std SAP , It is Not Possible..

Document Types and No. ranges

Hi Gurus,
How many types of document types should we have in a business?
If we have 5 banks and client wants number ranges of bank vouchers related to one particular bank should be in continuation, so How it should be done?
Please revert asap.
Thank You

Hi
Firstly, there is no fixed number of Document types, depending upon the need, the business can have any number of document types.
For your requirement, analyse the nature of transactions for every bank and create as many document types as the bank has if client wants to have the number range similar / in continuation along with the bank.
I know this is not practical. But atleast, you should try to minimise the number of transactions to be in line with the bank, so the number of document types you should create.
Thanks
Siva

SharePoint search using Term-IDs doesn't work as expected for various document types and items

If items or documents are tagged with managed metadata terms from the term store (no social tags, but pre-defined terms), you can find this content later on (after crawler has finished) using the following URL query:
http://myserver/search/Pages/results.aspx?k="85f915a2-bd9e-4c94-a840-4323d37e8df9"
The guid is the term ID (from the term store).
Issue:
That works great for office documents. It seems to be not working for several file types like txt, zip, aspx (inside page libraries) etc. All file types are generally registered with search crawler and are found correctly using the normal search, e.g. for
the term name or other content. It also not works for me with custom lists that are tagged with a term.
Questions:
1. Is using this type of search url a documented and advised feature, to find content that is tagged with terms?
2. How to setup search to find this items and documents consistently with "normal" search AND by term ID?
Thanks, Frank
Thanks, SharePointFrank http://www.layer2.de/en/products/

Hello Frank,
SharePoint contents tagged with managed metadata Terms can be searched by doing a search on “TermName”, and the search result could be refined by managed metadata. Please ensure your SharePoint site content source was crawled and Managed Metadata
Service Application was running. Personally, using a TermID involved in the URL to search items tagged with metadata isn’t advisable due to difficulties when manipulating a ID number.
Fabian Williams has included a managed metadata search section in his informative walk through:
http://www.endusersharepoint.com/EUSP2010/2010/06/01/understanding-managed-metadata-in-sharepoint-2010-its-impact-on-taxonomy-navigation-and-search-part-1-focusing-on-managed-metadata-term-store-navigation-and-search/
Let me know if I misunderstand you.
Thanks & Regards.
Lily Wu || Microsoft Online Community Support Engineer || SharePoint

For new document type for pur. requisition

Dear cons
We have created two series of purchase requisition i.e. - ph-1, ph-2 for project. For ph-1 pur Requisition we have created WBS element. Also for ph-2 we have created separate WBS element. When we create a pur. Requisition for ph-1 if we entered WBS element of ph-2 the system is accepting which is creating a problem. Our point is that system will only accept WBS element of the respective phase. That means for ph-1 pur. requisition the system will accept only ph-1 WBS element not ph-2 WBS element. So pl. give some idea so that we can solve the issue. So where can we make the setting so that the issue can be solved.
thnks
nrp

Hi Nirupama,
You can control this though authorization
Find out the authorization object for docuent type and account assignment
And assign allowed wbs for doc type , take basis help on this
BR
Diwakar
reward if useful

Field editable in FB02 for only one document type and user

Hi:
I have a question about editing a field and I hope you can help me. I need to make a field editable in FB02, but only for one document type and two users. The field is BSEG-ZFBDT, Baseline payment dte.
I have tried in ‘Document Change Rules’, make this field editable when line item not cleared, but it works for all document types and users.
Please, any idea?
Thanks in advance for your time.
Best regards.

Hi,
You have to write a ABAP code to achieve this.
Validation is another Option where you can mention that value is allowed in the Baseline Date field only if the User and Document type value satisfies.
BR
Amitash

When do we need a new document type in p.o

Hi experts,
can someone explain me when do i need new doc.type in p.o. what could be the scenario.
how to respond this question in interview.
Thanks

Hi
1) suppose you want separate report for import PO and domestic Po in t-code like ME2N,ME2L in that case we have to define new Po document type so we can get report by document type same will applicable to Asset purchasing also
2) you want different pricing procedure assignment in MM then in that case Po document will help like import and domestic pricing procedure
3) suppose IN service Po user may forget to use item categories D or he may used different item categorizes other than D so in that case we can define new document type and allow only item categories D so he can not use wrong item categories in PO
Regards
Kailas Ugale

BBP_BS_GROUP_BE for new document type and number range

Similar Messages

Maybe you are looking for