Classic - SAME PO number ranges in SRM PO via SC as well as ECC PO via PR

Hi
for example we do have PO
existing
PO 54XXXXX number serial creates via SRM by shopping cart
PO 55XXXXX number serial created PO via ECC system
but business now wants same number ranges for Both system Purchase orders WHATERVER IT MAY BE.
54XXXXXX only for SRM created PO as well as ECC PO .
SC IN srm PO in ECC 54XXXXX
PR-PO in ECC 54XXXXX
is it possible? TO HAVE SAME NUMBER RANGE
*CUSTOMER EXPECTS LIKE BELOW.*
*FOR EX PO 540000001 CREATED FROM srm by Shopping cart
*PO 540000002 CREATED BY ECC SYSTEM.via Purchase request or direct me21n*
HOW CAN I MAKE INTERNAL AS WELL EXTERNAL VIS DOC TYPE.
THEY DO NOT WANT TO HAVE TWO SEPARATE NUMBER RANGES FOR ONE BUSINESS OBJECTS. aNY ONE ACHIEVED IN REAL TIME?
br
Muthu

Thanks much Ahmed for confirmation on this.Appreciate you Ahmed on this help.
why i have asked this question we do create some PR from APO system. but their APO Purchase request uses same number range in the ECC system.
for eg. APO creates PR -300001
ECC creates PR -300002
but i dont know how it achieved in APO -ECC scenario.
Muthu
Edited by: Muthuraman Govindasamy on Jan 16, 2010 3:01 PM

Similar Messages

Extended Classic - Purchase Order Number Ranges

We are using Extended Classic EBP. When a PO is created in SRM the PO replicated into R/3 does not have the same number.
The backend PO document type is ECPO. We have assigned an internal and external number range to this document type.
When an SRM PO is replicated to the backend, the backend PO number is taken from the internal number range for the document type. This internal number range does not include the number range of the SRM POs.
We expect the SRM PO number to be pushed into R/3 and therefore the external number range of the R/3 document type should match the SRM PO number range.

Hi
No need to maintain the internal number range for the SRM PO document type ECPO in R3 (maintain the external number range code of SRM PO transaction type).
As the PO is created in SRM, and the number range you maintained in SRM and R3 should be same, but in SRM it will be internal number range and in R3 it should be external number range. (number range code should be same in both the systems).
Regards
Reddy

Classic & EC - PO & other purchasing documents number range

Hi SRM Gurus,
Can any one please explain me more precisely about number ranges in SRM & MM.
For classical scenario, we will define number ranges for PO & other purchasing documents in SRM as internal number ranges and in MM as external number ranges.
But in Classical scenario we will create POs (or other Purchasing Documents) in backend system. Suppose If it is to be replicated to SRM as per business need, then how system works. Because we defined in SRM PO number range as internal number range and in backend system as external number range.
Again in Extended Classical scenario, for MRP materials PR or Reservation will be created in backend system with internal number range. But in Plan-Driven scenario they will be replicate to SRM. In this case how we have to choose number ranges.
I am confused. I'll appreciate if any one explains me with step by step or with examples for Classic and Extended classical scenarios
Points will rewarded
Thanks,

Hi,
Please find my responses in bold below:
For classical scenario, we will define number ranges for PO & other purchasing documents in SRM as internal number ranges and in MM as external number ranges.
Sundeep: In Classic Scenario, you do not define number ranges for PO internally in SPRO. You would only define number ranges for shopping carts, Confirmation and Invoices if required. Please see description of classic and extended classic scenario below.
External number ranges are defined for PR's and PO's in ECC in a classic scenario environment. (No Internal number range is defined in SRM for these documents in classic scenario and a shopping cart is a PR in SRM)
So, basically in classic scenario, you create only a Shopping cart (Internal Number Range) and all follow on documents such as PR, PO etc are created as external number ranges in ECC, which are a result of a shopping cart from SRM having an internal number range locally.
But in Classical scenario we will create POs (or other Purchasing Documents) in backend system. Suppose If it is to be replicated to SRM as per business need, then how system works. Because we defined in SRM PO number range as internal number range and in backend system as external number range.
Sundeep: This scenario is not possible. In classic scenario you cannot replicate the PO back to the SRM system. Such a scenario is usually accomodated by an Extended Classic Scenario.
Again in Extended Classical scenario, for MRP materials PR or Reservation will be created in backend system with internal number range. But in Plan-Driven scenario they will be replicate to SRM. In this case how we have to choose number ranges.
Sundeep: In a Plan driven procurement the PR is created in SRM as a shopping cart with internal number range. (PR = Shopping cart in SRM). No reservations are created locally in SRM from a PDP. Reservation are only possible in a Classic scenario from SRM -> R/3.
· The classic scenario
The shopping cart is created and approved in SAP Enterprise Buyer. The remainder of the procurement process takes place in the backend ERP system(s) and all other follow-on documents, such the purchase order, goods receipt/service entry sheet and invoice, are located there. With SAP Supplier Self-Services, you have partial supplier involvement for the operational procurement business scenarios when buying materials. There is no support for services.
· The extended classic scenario
The shopping cart is created in SAP Enterprise Buyer. The purchase order and follow-on documents are also created there and then replicated to the backend system. The purchase order in SAP Enterprise Buyer is the leading purchase order and cannot be changed in the backend system. Goods receipts and invoices can be pre-entered in SAP Enterprise Buyer or entered directly in the backend system. With SAP Supplier Self-Services, you have partial supplier involvement for all your operational procurement scenarios. In these scenarios, you have supplier involvement for the purchase order and the purchase order response.
Hope this info helps !!
Pls assign points for usefull answers !!
Sundeep
Message was edited by:
Sundeep Ravande

Excise invoice and domestic invoice sharing same number range

Hi,gurus,my question is addresed to the sap cin gurus
Scenario:-- Normally sap has provided provisions that the domestic invoice and the excise for the export will have different number range object
Transaction-snum or snro(As per the rule the no range has to be approved by excise authorities)
Requirement:--The present requirement of the client is that as per their requirement they will be using the same excise number range both for domestic and the export(They have got the approval from the excise department as per the amendment,that specifies the same)
so i request you to pls guide me as how can it be done in sap that two different business process will share the same number range.
as per my knowledge local excise number range is-J_1IEXCLOC
and for exports is-J_1IEXCEXPand the both will use the same number range and,suppose 1 local invoice is created and say if the no is 1,then if the export excise invoice is created the number will be 2,pls guide me how is it possible that the same number range should be used.
Thanks in advance---Anshuman chakraborty

Dear sir,Thanks for attention towards the issue,but still i need to clarify some details-
the number range forJ_1IEXCLOC are already configured .It is not the case like i have to configure it for the first time however ,so the issue remains how shall i proceed in this case
Sir,i have already checked the transaction j1iin,it does not give any such box to check the-use local no range
infact the error message which the system was throwing to the user that-number range object not assigned for Object: J_1IEXCEXP.
The question remains from my side is what are the complete configuration steps I need to do ,to make the check box appear so as to select-use local number range,and is there any thing to be conveyed to my developer,so that the same appears,
or is it the case like the anything should earlier have been done before the number range for J_1IEXCLOC was created.i would request u to pls guide me giving the complete details of the step to be followed.
Thanks in advance
Anshuman chakraborty

Copy of leading document(PO) not having the same data as created in SRM

SRM5.0 Extended Classic Scenario
I have created the SC and PO for that is created successfully as 700006304.
Now when I am trying to create any SC after that, the leading document of EBP goes into error in process in follow on document block.
All the successive PO 7000063041, 7000063042 are going into error in process and displaying another data in the backend with the creation of goods/receipt and invoice.When I try to go into that invoice it says that it doesnot exist.
When I see in the backend found out that data that I have taken for creating the PO is not copied to ECC system , It displays some another data, may be fetching different PO data having confirmation and invoice detail which i have not done at the SRM side.
As we know that the leading document of EBP (PO) is copied to the ECC system in ECS( Extended classic scenario) but in our case I am surprised that from where it is fetching the different data for the copy of leading document in backend.
I have scheduled the two background jobs too mentined below even then this problem is not corrected.
1) BBP_GET_STATUS_2
2) ZCLEAN_REQREQ_UP
Kindly advice.
Edited by: SAP jayoti on Jul 1, 2010 11:36 AM

I have seen details in BBP_PD :-
For first PO its displaying workflow status complete & Document Completed. Its fine.
For the successive PO's - Status is Transfer Failed (E.Sys). But workflow status is complete.
I have checked the external number range at SRM and ECC side too.
At SRM side ,Number range set up for PO
From Number 7000000000 To Number 7999999999 Current Number 7000063059
At ECC ,Number range set uo for PO
No - 70, From Number 7000000000 To NUmber 7099999999 Current Number 'Blank'
External munber range is set at ECC for SRM PO.
There is no overlaps for the different document type PO range .
Kindly Advice.
Edited by: SAP jayoti on Jul 1, 2010 2:38 PM

External number range for purchase order response?

Hi all,
is it possible to use an external number range when creating purchase order responses (BUS2209, PCO, POR) manually?
If I transfer the POR from an external system like SUS via XML, can I use an external number range?
I'm using SRM 4.0 (EBP 5.0) in standalone scenario with Business Connector 4.7 as XML interface.
Any help is appreciated,
Karsten

Hi
No need to maintian Internal number range.. Yes you need to use an external number range
Only the PO, RQ & RS are sync and therefore must correspond with the R/3 number ranges.
The rest, Shop Cart (SC), Local PO (EBP), Confirmation, Invoice, Bid Inv and Bid, aren't synced and can be assigned to any number range. (FYI- using ECS)
Re: Extended Classic - Purchase Order Number Ranges
http://help.sap.com/saphelp_srm50/helpdata/en/87/7cc73cee4fb55be10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/6d/0f343e47fd6b2ee10000000a114084/frameset.htm
Re: Number range config
Re: config for Number Ranges ? :-(
Re: PO Creation with external PO number
Purchase Order Response BUS2232
PO number range Issue
Re: Defining the number range
Regards
- Atul

Vendor number range issue in BUCF transaction

Hi,
We are implementing the SRM 5.0 with Extended Classic scenario. I my current SRM system is already connected with 3 SAP R/3 system and I am implementing and adding 4th SAP R/3 system.
I am having an issue to replicating the vendor master from 4th R/3 system to our SRM system due to wrong number ranges in BUCF transaction code.
Current Number Range in SRM systems are:-
01     0010000000            0014999999     10003009
AB     0001000000        0009999999                        X     --> (7 Digits)
My new vendor master from 4th R/3 system is:-
0080000001        to     0080029999    --> (8 Digits)
My new vendor master number range is overlapping with my internal number range 01. As we know that we cannot reduce the lower range of 01 from 0010000000 to 0000000001. Also I cannot increase the number AB higher value from 0009999999 to 0099999999.
Can you any one please suggest me to correct the number range?
Thanks,
Senthil

Hello Senthill,
The vendor replication to external number ranges works as follows:-
(1) Cross-Application Components SAP Business Partner > Business Partne
> Basic Settings > Number Ranges and Groupings > Define Number Ranges
Here you sould define an external number range which corresponds to
the R/3 numbers. You may want to have more than one external range
in order to replicate all vendors.
(2) Cross-Application Components > SAP Business Partner > Business Part
> Basic Settings > Number Ranges and Groupings > Define Groupings and
Assign Number Ranges
For each replication run, you can download the vendors which correspond
to the external number range / grouping which is marked as 'standard
external'.
So, you will have to replicate your vendors separately for each number
range:-
Select the correct grouping each time by marking 'Ext.Std Grping'
and then run BBPGETVD for the vendors to be assigned to this grouping.
As standard, the customized settings for the number ranges
would have to be changed for each run of BBPGETVD and BBP_VENDOR_SYNC.
If you run the update or synchronization in combination with a
BADI the intervals could be taken into account.
The BADI is BBP_TRANSDATA_PREP
The methods are:-
Method: PREPARE_REPLICATION_DATA (intitial download)
Method: PREPARE_UPDATE_DATA (update)
Import data is stored in CT_LFA1 should be copied to an
internal table. There the required intervals can be determined.
This BADI is not assigned in the IMG but can be seen through SE18.
I hope this information is helpful.
Kind Regards,
Edel.

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

Business Partmer number ranges

Hi Gurus,
I would welcome others who have experienced the following issue with BP number ranges in SRM 5.
Basically, the system has been set so that when Business Partners are created by the system, for example end users, org plan nodes and so on, the system standard internal interval and number range 0000000001-0999999999 is used from t-code BUCF. Now the issue is, we are about to bring over our R/3 vendor records who also use the same number range, for example vendor number 300012 and as it is impossible to create two number ranges which overlap in customising t-code BUCF, even though the R/3 number range would be external.
Aside from using u201Cu201DInternal Number Assignment Onlyu201Du201D selection on BBP_VENDOR_GET_DATA, which I do not want to use, what other options are available in SRM 5 to get by this?
Thanks,
Steve Walsh

Hi
Here you need to understand what difference between vendor number and BP.
In SRM the system will recognize any object through BP only. and for vendor we need config a number rang in cross applicationsetting as like as in ecc. why becuase we stright way replicating the vendors from sap back end system. for accouting purpose we need the same number.
that we did we in cross application settings.
do write to me if you have any queries on this
regards
satish

2 external number range for vendor

Hello,
I am facing a problem when I try to replicate vendor from R/3.
I have 2 external vendor number ranges maintained in SRM, But only the last created external number range is taken into account when i replicate vendors from R/3.
Please could you tell me how can I maintain 2 external number ranges in SRM?
This is very urgent, I need to replicate vendors from R/3.
SRM 4.0 Extended Classic scenario.
Regards,
Shaiek

Hi Lina
You will have to combine all number ranges in R/3 and create one number range in SRM, if you want to retain the R/3 numbers.
e.g. If your R/3 number ranges are
100000 - 200000
600000 - 699999
In SRM, you need 100000-699999 as the external number range.
At any point of time, you can make only one no. range as default in SRM.
Best regards
Ramki

Excise Number range problem

i want to maintain the same excise number range for both EXPORT / Domestic,
how to do it .
Other things is while posting for the excise in SEZ case i am getting error===
ERROR in allocating excise invoice number interval not found number objetc J_1IEXCEXP.
plz guide it

Dear Rishi
Check my suggestion in this thread
[excise invoice and domestic invoice sharing same number range |Re: excise invoice and domestic invoice sharing same number range]
thanks
G. Lakshmipathi

Number range 01 is internal, do not enter a personnel number

Hi,
Im using PA40, and when I propose a personal number, the transaction sends this message "Number range 01 is internal, do not enter a personnel number"... BUT I NEED to propose a personal number for my employees!!!... is it possible???!!!...
Can anybody help me?...
Thanks in advance!.
Alfredo.

hi alfredo
see "Number range 01 is internal, do not enter a personnel number"... " if the message comes like this that means that particular number range is set for the internal number range i think so you are giving the personnel number if you remove that personnel number in IT0000 then save this case if you want to take the personnel number internal. if you want to take your personnel number then go to pa04 and assign personnel number range make it as external in the last column you can see there check box just click on that check box. and assign this same personnel number range (for ex you have given in pa04 07-00000000-10000000) the 07 in my example you have to assign in the numkr feature in TCODE PE03. in that assign countrygrouping-company code-personnel area-personnel subarea-ee group-eesubgroup- number range 07. i hope it is clear
bye
naveen

Document Number ranges

Dear All,
Pls help me to solve the issue reg document number ranges.
We have defiend the document number ranged for two company codes. Now ths issue is.. this document number range is being used/shared by both the company codes. For ex.. Invoice 01, 02 and 03 is posted in the company code A and we have not posted any Invoice in the Company Code B. If we post the Invoice in the Company Code B, number for the Invoice will be 04. And the next invoice in the Company Code A will be 05. But i will required to change the configuration to split the document number ranges..
Pls help me to do so.
Thank you

Hi,
This thing is obvious if the document number is being shared by more than one company code then it will act the following way...
for example :- Company code "A" is assigned with document number 01 and if you raise an entry it will take the range from 01...like document number generated will be 0000001
Company code "B" assigned with the same document number range 01 the next entry will create the next available number that is ....0000002
This happens b'cz its being shared by both the company codes.
Hence you have to keep seperate document number range for both the company code to avoid this confusion.
Please assign points.
Zia.

Document number ranges in entry view and in General Ledger view

What is the difference between Document number ranges in entry view and in General Ledger view ?
We have new GL activated in our system , and found that the GL Document types ( SA) are assigned to document number ranges in entry view . What is the need to define document number ranges in General Ledger view ?

Hi,
Document Number Range in entry view is the document numbers which are posting in your leading ledger. You cant achieve the same document number range to the general ledger view. A General ledger view can have both Leading ledger view and non leading ledger view therefore document number range should not be kept same for both ledgers as your running document number gets skipped.
That to some times you can only post documents to only Non Leading ledgers. Therefore a separate number ranges needs to be created for general ledger view
Hope u understood.
regards
srikanth
Edited by: boddupalli srikanth on May 21, 2009 9:28 PM

How to Use Same Asset Number with Different Sub-number

Hi
We want to sell some assets and buy them back on lease. We want to use same Asset number with different sub-number under the same company code. This new asset will be under different Depreciation Area (Statistical).
We use external numbes for assets . And same asset number range is used by all compnay codes.
Please suggest whether this is possible & how.
With Regards,
Nitin

Hi,
Go to field status for asset master data section and change the field status to optional for field Deactivation date, then follow the below steps.
You can create an sub asset number to an asset, which is already deactivated by retirement as like normal sub asset creation with AS11.(While creating sub number, you need to remove cap date and deactivate dcate field manually from asset master)
With this you can get new asset number as same as your old retired asset main number and but sub number will be different.
To post to diff dep area, other than 01, then you first create an acq transaction type, which will post only to specific areas and then use the new asset number in ABSO to post acq with your custom TTY.
I have tested and found working well in my system............Try now in your test client
Thanks,
Srinu

Classic - SAME PO number ranges in SRM PO via SC as well as ECC PO via PR

Similar Messages

Maybe you are looking for