VL10B ERROR -REG - STO "

Hi all ,
AM INTO S &D.
well i have configured STO btvn 2plants with in same co code.
well the purchase order(me21n) is saved with no errors and in ME23 the quantity ,receving & supplying plant details are projected.
CONFIGURATION :
ASSIGN DELIVERY TYPE &CHECKING RULE:
The doc considered is UB - NL - 01 checking rule.
THE SAME DOC IS ASSIGNED TO RECEVING & SUPPLYING PLANT .
MAINTAINED XK01,& XD01.
STOCK IS AVAILABLE IN SUPPYING PALNT.
CAN U PL LET ME KNOW THE PURCHASE DOC NUMBER IS NOT PROJECTED IN VL10B & ITS BLANK . EVEN THOUGH P.O DETAILS MAINTAINED IN VL10B.
THANKS,
JERRY .

Hi Kalyan,
    Thanks for the immediate response,
well , the devilery date creation is n grey mode(DEL CRE DATE) , but in the delivery schedule tab of STO (me21n), del date is projected as 25.06.2008 & committed date is 25.06.2008 with committed qty 20.
     And in vl10b considering the cal rul for del " 2" today & tommorow. and with input of p.o number stl the delivery no is not projetced.
   checked co09, stock is avaliable in plant & strg loc.CHECKING RULE DEFINED IN MM01 ,02 IND REQ.
picking location has been determined.
But stl the devilery no not being triggered in vl10b, moreover no error log shown in vl1ob.
Thanks,
Jerry.

Similar Messages

VL10B Error

Hi All
Iam getting an error during VL10B
Error Description:
All PBT resourses are currently busy.
Diagnosis:
The system tried to initialize the environment for processing parellel RFC using the function module SPBT_INITIALIZE.No resourses in the system which are necessary for processing this resourses.
Procedure:
Add more servers
Please guide me through this error. Iam using SAP 4.7C
Regards
Jagadish

Hi
The error seems to be reg the basis side.
Check whether u have ticked parallel processing in the third tab of VL10B screen wherein u will enter the parameters of the transaction .
If so remove the tick and then run the transaction.
Chk and revert.
Reg
Raja

Strange Error in STO

Hi
I am facing strange Error in STO.
I have 2 plants 2001 at Pune and 2004 at Nashik.I want to do STO from Nashil to Pune.
Accordingly in config for STO I gave supplying Plant as 2004 and receiving plant as 2001.
Then I manitained delivery type NL for Supplying Plant 2004.
Then I maintained Customer number in the plant details.for Pune Plant Customer Code 13 is created while for Nashik Plant 14 is created.
After all this config if I go and create PO with doc type UB and supplying plant as 2004 then the error message is generated no shipment data in found.
But on the other hand if I give supplying plant as 2001 and receiving as 2004 then I am able to create PO.
I checked again and again if there is wrror in config but it is exactly as per mentioned above.
Can anybody let me know the soln?
Regards

Hi,
u have to maintain shipping data so that shipping pnt determination can happen.
just chek the following settings in customization :-
1.The customer which you have created , in it shipping data chek (in customer master)whether u have put shipping condition and delivery plant.
2. in the material master you have maintained the loading group.
3.Create shipping pont
SPRO- Definition-Logistics Execution ---Choose Define, Copy, Delete, Check shipping point
4.Assign shipping point to Supplying plant (Under Enterprise Structure- logistics execution).
5.Assign shipping point to supplying plant again
SPRO-Logistics Execution-Shipping-Basic shipping Functions-Shipping point & goods receiving point determination---Assign shipping points
Hope it will solve ur problem
reward if useful
Rohit

VL10B error WITH REG STO .

Hi all,
well configuring STO btvn 2plants within co code.
IMG config :
doc" ub " suplying plant 2345 , del doc .
nl and chking rule 02 "
suplyng plant & recving plant assignd to UB "
IN me23 display P.O ,suppying & receving plant details are accurate with order quantity.
well , in the delivery schedule tab of STO (me21n), del date is projected as 25.06.2008 & committed date is 25.06.2008 with committed qty 20.
ERROR :
And in vl10b considering the cal rul for del " 2" today & tommorow. and with input of p.o number stl the delivery no is not projetced.
checked co09, stock is avaliable in plant & strg loc.CHECKING RULE DEFINED IN MM01 ,02 IND REQ.
picking location has been determined.
But stl the devilery no not being triggered in vl10b, moreover no error log shown in vl1ob.
could anyone pl guide , stl any config 2b completed in MM .
Thanks,
Jerry.

Hi,
In VL10B transaction remove the calculation rule for delivery and check whether you are able to create outbound delivery or not ?
Hve you assigned the shipping point to the plant and shipping data to the plant in STO configuration ?
Hope its clear.
reg
Durga
*assign points if the info is useful

Run time error while doing VL10B transaction for STO

Dear All,
We are facing problem of run time error while creating Delivery (VL10B) for STO .We have two company codes .For one company code its working fine .But we are trying for another company code ,this error coming.error detals
Error in the ABAP Application Program
The current ABAP program "SAPLV05I" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not cau
     in
    procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAI
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
Kindly suggest as to how to resolve this asap.
regards
umesh

These Kind of Errors Generally Occor for the wrong maitnaince of the partner functions. If you are using any user exits to detremine the partner functions. check the logic in that routine.
Because we do frequently get this error, but only if we hae not maintained as per the rule written in the user exit..
The USer exits for partner Determiantion to check is Function Module EXIT_SAPLV09A_003. THis gets activated, if you have give the source parner function as "X/Y/Z" in your partenr determiantion procedures.

Excise Invoice Error in STO from Manufacturing to Manufacturing Plant

Hi,
This is a scenario of Intracompany (within a company) STO from one manufacturing to another manufacturing Plant. Steps involved are
ME21N: STO Creation with doc type UB
VL10B: Outbound Delivery
VL02N: PGI (Mvt Type 641)
VF01: Billing
J1IIN: Excise Invoice
MIGO: Goods Receipt in Receiving Plant
The problem is while doing Goods Receipt (MIGO) wrf Outbound Delivery in Receiving Plant when we refer the Excise Invoice (created in J1IIN) we are getting an error message as u201CExcise Invoice 2000000033 31.05.2011 of Vendor 1300003 does not exist for Referenceu201D
Customer and Vendor master for the plants as well as STO configuration seems to be complete but still we are getting this error message.
Can anyone provide some idea how to resolve this?
Thanks in advance

Hi
when we refer the Excise Invoice (created in J1IIN) we are getting an error message as u201CExcise Invoice 2000000033 31.05.2011 of Vendor 1300003 does not exist for Reference
If I am not wrong in J1IIN ,you get two number ,one will be internal number try to capture with internal number
Regards
Kailas ugale

Error in STO while creating Deliveries.

Hi,
When we run VL10B in background few error messages are produced " Material staging date replaced by current date" and its error message.
STO contains around 100 line items, but error is produced for some line items only. I tried to find it out why it is happening but couldn't.
Where should i check it? Is there any customization or else to be checked?
Please guide me as its urgent issue.
Regards,
VS

Hi,
Create delivery in foreground by using VL04, analyse the error,If possible send error message.
Regards
Ravi shankar.
Edited by: Ravi Shankar H N on Jun 17, 2008 4:30 PM

Error in STO Process

Hi all ,
use made a mistake in the STO process.
process done as follows
STo created (inter company)
delivery created
Gi done
billing done
GR done (at receving co code and plant )
now due to some mismatch in values user at supplying plant has cancelled the billing then PGI and then deleted the delivry
now we want to create new delivery and but blank entry in VL10B
also when i try to cancel GR at receving plant it shows error cannot update delievry document
please let me know how can i cancel GR and do the complete process again
refred many threads but of no use
regards
Kunal

Hi,
Try the following procedure. It may work but it is highly not recommended:
1. Use t.code UASE16N.
2. Enter the table MKPF and press ENTER.
3. Enter the material document number (GR document number) and press ENTER.
4. Now type &SAP_EDIT in the command prompt and press ENTER.
5. Click on Execute button (F8).
6. Remove the value from the field "Reference" and SAVE.
7. Follow the above procedure from step 1 till 6 for the table MSEG. Remove the value from the field "Delivery".
8. Now try to reverse the GR.
Test this scenario in development client, analyse the implications and proceed.
Regards
Guru
Edited by: Guru Prasad on Mar 29, 2011 12:17 PM

VL10B - error on running in developement server

Dear Gurus,
We have created a new plant (Sales Depot) in our developement sever. It working fine when we are rasing STO/ PO for this particular Plant. But when we try to create OBD using VL10B, it through error messege "Inconsistency between DDIC types "SHP_VL10_EKKO_T" and "EKKO"". Then we tries VL10B for all existing plants and get the same error. Can any help to remove this error and back to it normal. Thanks in advances.

Hi,
Check SAP Note 1167784, hope this will help.
Prashant Rathore.

Excise Invoive doc error for STO: Intracompany

Dear Gurus,
I have executed the STO process between plant of same company code say Plant A: Normal manufacturing plant and Plant B : Depot.
I have created the PO for plant B ->Outbound delivery from plant A->Picking->PGI -> and posted the excise invoice through J1IS.
Now, while doing GR for the receiving plant for depot, I have selected excise invoice tab: Create RG23d entry, system gave me warning msg: excise invoive doesn't exit in the supplying plant (4F281). and proceed further and posted the GR.
Now while executing incomming excise invoice for depot receiving plant: J1IEX for the following combination I am getting the error:
1) Carture excise invoice --- Goods receipt (error msg: The material doc has already been refered for diff excise invoice)
so I tried to post with
2) Post -
Vendor excise Invoice-----(error msg: No part 1 exists for avaling credit in excise invoice 11 2009).
Kindly clarify my doubts.
Regards,
Prashanth Pai

this is SAP bug
while u r posting MIGO and capturing RG23D reg and giving excise invoice number that have come form mfg plant
in excis tab u wll have to give correct inviove number
in manuf plant have send excise invoing number 1234 31/12/09
in migo in excise screen in excise number u have to give 000001234 and in date 311209
traling zeros is very important
hope this solves ur issue

VL10b Error in EHP5

Dear Guru's,
We currently doing some test in EHP5 environment and facing problem when running tcode VL10B
Message of the error is "Internal error found ==> see syslog"
It also gives message in ST22
"No more storage space available for extending an internal table."
First I think it was a Basis issue, but after Basis team allocated more memory the problem still occurs.
Please advice
Regards,
AT

Hi Sunny,
Bellow are the complete shortdump
Short text
    No more storage space available for extending an internal table.
What happened?
    You attempted to extend an internal table, but the required space was
    not available.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    Try to find out (e.g. by targetted data selection) whether the
    transaction will run with less main memory.
    If there is a temporary bottleneck, execute the transaction again.
    If the error persists, ask your system administrator to check the
    following profile parameters:
    o ztta/roll_area            (1.000.000 - 15.000.000)
           Classic roll area per user and internal mode
           usual amount of roll area per user and internal mode
    o ztta/roll_extension       (10.000.000 - 500.000.000)
           Amount of memory per user in extended memory (EM)
    o abap/heap_area_total      (100.000.000 - 1.500.000.000)
           Amount of memory (malloc) for all users of an application
           server. If several background processes are running on
           one server, temporary bottlenecks may occur.
           Of course, the amount of memory (in bytes) must also be
           available on the machine (main memory or file system swap).
           Caution:
           The operating system must be set up so that there is also
           enough memory for each process. Usually, the maximum address
           space is too small.
           Ask your hardware manufacturer or your competence center
           about this.
           In this case, consult your hardware vendor
    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each dialog process.
    Parameters for background processes:
    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
           Extended memory area from which all users of an
           application server can satisfy their memory requirement.
Error analysis
    The internal table "\FUNCTION=SHP_LIKP_SELECT_02\DATA=CT_LIKP" could not be
     further extended. To enable
    error handling, the table had to be delete before this log was written.
    As a result, the table is displayed further down or, if you branch to
    the ABAP Debugger, with 0 rows.
    At the time of the termination, the following data was determined for
    the relevant internal table:
    Memory location: "Session memory"
    Row width: 2864
    Number of rows: 1845456
    Allocated rows: 1845456
    Newly requested rows: 4 (in 1 blocks)
    Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server prt02ec_P2S_00 on host prt02ec (wp 5)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 2232
    The error reported by the operating system is:
    Error number..... " "
    Error text....... " "
How to correct the error
    The amount of storage space (in bytes) filled at termination time was:
    Roll area...................... 6221072
    Extended memory (EM)........... 3469161024
    Assigned memory (HEAP)......... 2000761376
    Short area..................... " "
    Paging area.................... 0
    Maximum address space.......... 18446744049921009200
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TSV_TNEW_PAGE_ALLOC_FAILED" " "
    "SAPLLE_SHP_DB_DELIVERY_BUF_EXE" or "LLE_SHP_DB_DELIVERY_BUF_EXEU11"
    "SHP_LIKP_SELECT_02"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
System environment
    SAP Release..... 702
    SAP Basis Level. 0009
    Application server... "prt02ec"
    Network address...... "10.1.7.60"
    Operating system..... "SunOS"
    Release.............. "5.10"
    Hardware type........ "sun4u"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 5
    Shortdump setting.... "full"
    Database server... "prt02ec"
    Database type..... "ORACLE"
    Database name..... "P2S"
    Database user ID.. "SAPPEP"
    Terminal.......... "AllanTheGreat"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Oct 16 2011 21:41:26"
    create on........ "SunOS 5.9 Generic_122300-28 sun4u"
    Database version. "OCI_102, 10.2.0.4.0, V3 "
    Patch level. 109
    Patch text.. " "
    Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
    SAP database version. 720
    Operating system..... "SunOS 5.9, SunOS 5.10, SunOS 5.11"
    Memory consumption
    Roll.... 6221072
    EM...... 3469161024
    Heap.... 2000761376
    Page.... 0
    MM Used. 5302533992
    MM Free. 168458384
User and Transaction
    Client.............. 100
    User................ "ALLANT"
    Language key........ "E"
    Transaction......... " "
    Transaction ID...... "4EC3C0DF7CC71D8EE10000000A01073C"
    EPP Whole Context ID.... "8021287E578F1ED184864F59ADB45A42"
    EPP Connection ID....... "4EC3C0F77CC71D8EE10000000A01073C"
    EPP Caller Counter...... 1
    Program............. "SAPLLE_SHP_DB_DELIVERY_BUF_EXE"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Debugger Active..... "none"
Server-Side Connection Information
    Information on caller of Remote Function Call (RFC):
    System.............. "P2S"
    Installation Number. " "
    Database Release.... 702
    Kernel Release...... 720
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "asynchronous with reply and non-transactional (emode 0,
     imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. 100
    User................ "ALLANT"
    Transaction......... "VL10X"
    Call Program........."SAPLV50R_VIEW"
    Function Module..... "SHP_VL10_DELIVERY_CREATE_PARA"
    Call Destination.... "prt02ec_P2S_00"
    Source Server....... "prt02ec_P2S_00"
    Source IP Address... "10.1.7.60"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note:
    - For Releases < 4.0, information on the RFC caller not available.
    - The installation number is available from caller Release > 700
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note: For releases < 4.0, information on the RFC caller are often
    only partially available.
Information on where terminated
    Termination occurred in the ABAP program "SAPLLE_SHP_DB_DELIVERY_BUF_EXE" - in
     "SHP_LIKP_SELECT_02".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 14
    of the (Include) program "LLE_SHP_DB_DELIVERY_BUF_EXEU11".
Source Code Extract
Line SourceCde
    1 FUNCTION SHP_LIKP_SELECT_02.
    2 *"----
    3 ""Lokale Schnittstelle:
    4 *"       IMPORTING
    5 *"             REFERENCE(IT_LIKP_KEY) TYPE SHP_VL10_LIKP_KEY_T
    6 *"             REFERENCE(IF_SORT) TYPE XFELD DEFAULT 'X'
    7 *"       CHANGING
    8 *"             VALUE(CT_LIKP) TYPE SHP_VL10_LIKP_T
    9 *"       EXCEPTIONS
   10 *"              NO_RECORD_FOUND
   11 *"----
   12 * For buffered select use FunctionGroup V50R !!!
   13
>>>>>   SELECT * FROM LIKP
   15            INTO TABLE CT_LIKP
   16            FOR ALL ENTRIES IN IT_LIKP_KEY
   17            WHERE   VBELN = IT_LIKP_KEY-VBELN.
   18
   19   IF SY-SUBRC <> 0.
   20     MESSAGE E551(VR) WITH 'LIKP' RAISING NO_RECORD_FOUND.
   21   ELSEIF IF_SORT = 'X'.
   22     SORT CT_LIKP BY VBELN.
   23   ENDIF.
   24 ENDFUNCTION.
Edited by: Allan Taufiq on Nov 16, 2011 11:23 AM

Vendor error in STO ????

Hi,
I am doing Stock transfer from plant to plant in same company code. I have done STPO >DLV>INV>Ex. INV
at the time of MIGO ia mfacing some problem. i have maintain all the information in the Excise TAB of migo but still face the following errors.
1.Maintain Vendor for the excise invoice. (Message No 4F185) ...????
How we can view particular message no. on the SDN site to get more information ?
Thanks in advance
SAP-MM

hi
i think ths question is repeted by u ,
Maintain vendor for excise invoice -STO process??
u just maintain the excise indicator and try
take help of following thread for process
Returns - STO from PLANT to DEPOT
regards
kunal
Edited by: SAP Learner on Feb 3, 2010 12:03 PM

Error in STO

Hi all,
While doing Goods Receipt against an STO, the system shows the message:
"MSSA-SATRA exceeded by 500 SET"
I have done 351 movement to post the stock in stock in transit.The qty which is to be sent is correct.
Please give some solution.
Regards,
Sunny

Hi sunny
Although you created a stock transfer order with account assignment to a sales order, you can change the requirements type in the sales order item. However, a change should only be permitted if the new requirements type has the same 'Indicator: valuation of special stock' as the stock transfer order (VBAP-KZBWS = EKPO-KZBWS).
Otherwhise, the following error messages may occur after you change the requirements type in the sales order if you post a goods movement for the stock transfer order:
M7 022 "MSSA-SATRA exceeded by & & &"
M7 021 "Deficit of & & & MSSA-SATRA."
The above comment is as per note No 375063.
Check it out.
Regards
Prasad
Reward if useful.

MIGO ERROR IN STO

Hi,
While creating MIGO in STO process,we are getting error "Maintain Vendor for the excise invoice"this is the first time we are doing in our company
STO-2PLANT in 1Sales Org
Process
1)ME21N
2)VL01N
3)VF01
4)J1IIN-for Excise posting
5)MIGO
Every thing is ok up to J1IIN but while creating MIGO i am getting that error.
Regds
NAG

Dear Naga,
Perform few checks:
Customer Code at both the places must be same.
Note-down the Customer Code assigned to the Supplying Plant,in:
SPRO --> MM --> Purchasing --> Purchase Order --> Set up Stock Transport Order --> Define Shipping Data for Plants
Now, Go to, T. Code: XK02
Here, in to Screen: Control, assign the Customer Code and Save.
Maintain the Vendor Excise-Details in T. Code: J1ID.
Maintain Condition Record in T. Code: FV11
Best Regards,
Amit

No goods issue can be posted- error in STO

Dear Experts,
I am trying to post GI for an outbound delivery in VL02N.
This delivery was created when I did Goods Issue in MB1B using Mtype : 352 for a Stock Transfer Purchase Order
Kindly note that my Storage Location is WM+HU Managed. I confirmed TO aslo.
While I am trying to do PGI for outbound delivery in VL02N, I am encountered with the error " For item 00010 of purch. order 4500000901, no goods issue can be posted ---   Message no. M7152"*
I am using a PO type for Stcok Transfer and also Item Category is U in PO Line
Kindly help me.
Regards,
Shetty

Hi Shetty,
Can you please review the notes as a possible solution for your issue:
14912 MB1B FM: M7152 No goods issue possible
352735     MIGO for Stock in transfer
Please check following information whether they explain your system
behaviour:
- The document 'UB', with item type 'U', is used just for stock
transfer order within the same company.
- On SD side, the following document types can be used:
NL      Replenishment delivery (without billing document)
          corresponding dummy Sales order DL/NLN(item cat.)/NN(sch.line
NLCC    Cross-company-code replenishment delivery (with bil.document)
          corresponding dummy Sales order: DL/NLC(item cat.)/NC(sch.line
- On MM side
UB Stock transport ord., with "U" item category
NB Standard PO, with "blank" item category
641/647 for STO              assigned to SD schedule line cat NN
643/645 for cross-company    assigned to SD schedule line cat NC
In the standard system, the delivery type NL is used for inter-plant
stock transfer without billing document. For such transfer with
carried out with billing documents, the delivery type NLCC is used.
If you choose 'UB', this means that a stock transfer is to take place
without a billing document. Choose 'NB' if a purchase order involving
delivery and billing document is to be issued.
A combination of delivery type NLCC with purchase order type UB
would not be valid.
In Purchasing,if you create a PO in ME21N where supplying plant and
receiving plant belong to one company code the system will us UB.
If you create a PO where the 2 plants belong to separate company codes
the doc type NB is used.
Best Regards,
Arminda Jack

VL10B ERROR -REG - STO "

Similar Messages

Maybe you are looking for