Quantcast
Viewing all 1703 articles
Browse latest View live

unable to delete supply chain unit

Dear All ,

                   The supply chain unit deletion log in SLG1 gives the below error . SCU is defined as type 1003 and there is no corresponding location in /sapapo/loc3.

 

@5C\QError@ Error while deleting supply chain unit SP1000

@5C\QError@ SCU SP1000 is still used in delivery environment

 

                   

Thanks,

Shubh.


Activity Area

Dear Experts,

Could you please help me to understand use of activity area in real time perspective?

I knew that it is logical grouping of storage bins, but what exactly it is useful?

for example, i can understand use of storage section in real time. storage section also kind of grouping storage bin based on attributes, so we can use it during put away like fast moving or slow moving.

But i couldn't figure out use of activity area in real time, could you please help me to understand?

 

Thanks and Regards,

Prabakaran Gurusamy

Bulk storage putaway rule

Dear SAP Gurus,

 

      In business of cold storage W/H , if there are several HU type is managed in the warehouse no. and the putaway strategy is "Bulk storage". The system will suggest the destination bin by the "Bulk Structure"

 

      However, if the user mixed HU type in the same bin location, as found the system didn't calculate the number of HU by the bulk structure as usual. Has anyone know how the system logic will suggest the destination bin for Bulk storage?

 

 

 

Rgds,

Pat

EGR with duplicate docs

Dear SAP Gurus,

 

         When performed EGR (Expected Goods Receipt), we found system allowed to create duplicate document from the same PO/Production order. How to set program can check and block any documents that already converted to EGR?

 

 

        

Rgds,

Pat

Posting GI and GR on EWM doc

Dear SAP Gurus,

 

        We are facing issue about posting GR or GI on EWM Inbound / Outbound doc unable to be back date. Has anyone suggest if it possible to define Actual date of GR or GI to be previous date , previous month? Purpose is concerned with month end closing.

 

 

Rgds,

Pat

Credit limit not block GI posting in EWM

Dear SAP Gurus,

 

    During outbound delivery process in SD they set credit limit to block GI. However, when interface outbound document to EWM. We expected if GI posting on EWM should be blocked as well but we still be able to post GI and system sent GI posting doc to ECC. Any suggest if we can do blocking for this matter?

 

 

Rgds

Batch characteristics on GR process

Dear SAP Gurus,

 

      Anyone can suggest on std. trx. /SCWM/PRDI and /SCWM/GR to perform GR, is there any field to input batch characteristics for Inbound delivery doc?

 

 

Rgds,

Pat

AUTOMATION OF INBOUND PROCESS

Hi all,

 

how to do automation of Inbound Process. i.e i want to upload the data from file, then In Inbound Process it should execute Unloading, GR, and Putaway should complete system itself.


Goods movement bin of delivery items in a HU must be uniform.

Hi experts,

 

While creating Inbound delivery order  EWM, im getting the following error,

 

 

 

Goods movement bin of delivery items in a HU must be uniform.

 

Regard

EGR in EWM : how to block PO if not yet released

Dear EWM Gurus,

 

        PO from ECC not yet released but when EWM run EGR program it can be generate inbound delivery. Has any filter or config setting to block / not allow to create inbound in EWM side?

 

 

Rgds,

Error message in qRFC when GI from EWM

Dear EWM Gurus,

 

        We've found error during interface GI posting from EWM to ECC with error message below in SMQ2 (inbound queue monitor). Could you please advise how to solve?

 

Procedure

Cancel current processing.

 

Contact your system administrator.

 

Action to be taken by the system administrator

 

Check in Customizing for Inventory Management under Copy, Change Movement Types whether the entry is contained in the Update control view for the movement type.

 

If the entry is missing, proceed as follows:

For standard movement types, this means that the given process is not supported using the present data combination. Do not create any entries without prior arrangement with your SAP consultant. Otherwise, incorrect postings may result.

 

For customer-defined movement types (beginning with 9, X, Y, or Z), this may mean that they have not been fully defined. Delete the movement type and re-create it by copying a standard movement type.

 

 

Rgds,

EGF DRILL_DOWN in Chart Stacked Columns

Hi EGF experts,

 

 

I have create an chart with stacked columns.

 

Image may be NSFW.
Clik here to view.
stacked_columns.gif

 

On X-Axis there storage section with 2 series (number of free and filled bins). I want to click on an column (drill down) and popup a chart with details, but i get no information in the import parameter 'IS_POINTS' which ID (storage section) I have selected, only the index is filled. the an normal column chart works fine.

 

Image may be NSFW.
Clik here to view.
is_points.gif

 

I use the same method 'ADD_SERIES_GENERAL' in both chart types.

 

 

Thank you in advance for your help.

Selection of blocking indicators

Hello

 

When running the transaction "LS06" on the selection of blocking indicator I have this field where I get more options.. if I select "All" to block all my storage bin results this : "If you select this field, the system displays all storage bins, whether they are blocked or not. It does not take the blocking indicators for stock placement or stock removal into consideration."

 

What means in this case stock placement and stock removal?

 

Thank you

Error in EWM on posting expected good reciept

Dear All,

                   On posting expected goods receipt from ECC , i am getting the following error in log .

 

@5C\QError@ Messages for Item: GRN 1

@5C\QError@ Field Item: Product is a required field for the action HDR: Activate Document              

 

                     Due to this on search of purchase order in /n/SCWM/GRPE , i am not getting the corresponding EGR in EWM. Could you please let me   know the error cause.

 

Thanks,

Shubh.

Mapping between Carrier and Freight Terms

Hello Experts

 

 

My requirement is to get all the available carriers and their respective allowed Freight Terms for DC.

Does mapping maintained in ECC or EWM because both are coming from ECC to EWM.

Also is there any Table maintained in EWM for this?

 

 

Thanks

Akhil


Hi expert, i am executing t.code in dev sys it is working fine. but same t.code is giving short dump

Hi expert,

 

i am executing t.code in dev sys it is working fine. but same t.code is giving short dump in prd system.

 

please help me out asap.......

 

 

Thanks in advance............

In prd t.code is giving short dump

Hi Expert,

 

In dev system t.code is working fine. but same t.code in prd gives short dump. please advice me what will be the possibility for dump.

 

Please help me out.......

 

Thanks in advance........

EWM integrate with QM inspection type

Dear EWM gurus,

 

     If the ECC separate the inspection type by processes, such as inspection from GR for order, inspection from other GR, recurring inspection, inspection for delivery etc.

     In the ECC help explained the standard inspection type for interface with EWM is "17", in this case should we separate the inspection type by processes or not such as 1701, 1702, 1703...?  Kindly suggest.

 

Rgds,

EWM Upgrade from 9.1 to 9.3 on SCM7

Hi Experts,

 

We are performing EWM system upgrade from 9.1 to 9.3, which is on SCM system with 7.0 EHP3. At XPRA_AIMMRG phase we are facing below error. Kindly help us to solve this.

 

We have already implemented the SAP Note 2196031 - ASSERTION_FAILED dump during client copy, install or upgrade manually by unlocking the system, but still we are facing the same.

 

Thanks in advance!!

 

XPRAUPG error

 

XPRA ERRORS and RETURN CODE in SAPR740XPRA90000090.E91

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 ETP109 version and release : "380.28.39" "742"

1 ETP198

2 EPU126XPost-import methods for change/transport request: "SAPK740XPRA90000090"

4 EPU111    on the application server: "CTSC005113289"

2 EPU122XPost-import method "/SCMB/DF_GENERATE_AFTER_IMPORT" started for "/SCMB/V_DF_DCTP" "V", date and time: "20151128215522"

1AETR012XProgram canceled (job "RDDEXECL", number "21552200")

1AEPU320 See job log"RDDEXECL""21552200""E91"

1 ETP111 exit code           : "12"

>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<

 

 

XPRAs are application reports that run at the end of an upgrade.

Most XPRA reports have a report documentation that explains what

the report does and how errors can be corrected.

 

 

Call transaction se38 in the SAP system, enter the report name,

select 'Documentation' and click the 'Display' button.

>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<

 

ST22:

 

Category               ABAP Programming Error

Runtime Errors         ASSERTION_FAILED

ABAP Program           /SCMB/CL_DF_DOCUMENT_TYPE=====CP

Application Component  SCM-BAS-DF

Date and Time          28.11.2015 16:09:22

----------------------------------------------------------------------------------------------------

 

 

----------------------------------------------------------------------------------------------------

|Short Text                                                                                        |

|    The ASSERT condition was violated.                                                            |

----------------------------------------------------------------------------------------------------

 

 

----------------------------------------------------------------------------------------------------

|What happened?                                                                                    |

|    The current application program has detected a situation with the                             |

|    ASSERT statement that should not occur.                                                       |

|    The reason for this runtime error was one of the following:                                   |

|    - For the checkpoint group specified with the ASSERT statement, the                           |

|    activation mode is "abort".                                                                   |

|    - A system variant has been used to set the activation mode to "abort"                        |

|    globally for all checkpoint groups in this system.                                            |

|    - The activation mode is set to "abort" at program level.                                     |

|    - The ASSERT statement is not assigned to any checkpoint groups.                              |

----------------------------------------------------------------------------------------------------

 

 

----------------------------------------------------------------------------------------------------

|What can you do?                                                                                  |

|    Note down which actions and inputs caused the error.                                          |

|                                                                                                  |

|                                                                                                  |

|    To process the problem further, contact you SAP system                                        |

|    administrator.                                                                                |

|                                                                                                  |

|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |

|    at and manage termination messages, and you can also                                          |

|    keep them for a long time.                                                                    |

----------------------------------------------------------------------------------------------------

 

 

----------------------------------------------------------------------------------------------------

|Error analysis                                                                                    |

|    The following checkpoint group was used: No checkpoint group specified                        |

|                                                                                                  |

|    If the FIELDS addition was used in the ASSERT statement, you can find                         |

|    the content of the first 8 fields specified in the following overview:                        |

|     (not used)                                                                                   |

|     (not used)                                                                                   |

|     (not used)                                                                                   |

|     (not used)                                                                                   |

|     (not used)                                                                                   |

|     (not used)                                                                                   |

|     (not used)                                                                                   |

|    " (not used) "                                                                                |

----------------------------------------------------------------------------------------------------

 

 

----------------------------------------------------------------------------------------------------

|How to correct the error                                                                          |

|    Probably the only way to eliminate the error is to correct the program.                       |

|    -                                                                                             |

|    If the error occurs in a non-modfied SAP program, you might be able to                        |

|    find a solution in the SAP Notes system. If you have access to the SAP                        |

|    Notes system, check there first using the following keywords:                                 |

|                                                                                                  |

|    "ASSERTION_FAILED"                                                                            |

|    "/SCMB/CL_DF_DOCUMENT_TYPE=====CP" bzw. /SCMB/CL_DF_DOCUMENT_TYPE=====CM004                   |

|    "TABLE_CREATE"                                                                                |

|    If you cannot solve the problem yourself, please send the following                           |

|    information to SAP:                                                                           |

|                                                                                                  |

|    1. This description of the problem (short dump)                                               |

|    To do this, choose  System -> List -> Save -> Local File (unconverted)                        |

|    on the screen you are in now.                                                                 |

|                                                                                                  |

|    2. A suitable system log                                                                      |

|    To do this, call the system log in transaction SM21. Restrict the time                        |

|    interval to ten minutes before the short dump and five minutes after                          |

|    it. In the display, choose System -> List -> Save -> Local File                               |

|    (unconverted).                                                                                |

|                                                                                                  |

|    3. If these are programs of your own, or modified SAP programs: Source                        |

|    code of these programs                                                                        |

|    To do this, choose  More Utilities -> Upload/Download -> Download in                          |

|    the Editor.                                                                                   |

|                                                                                                  |

|    4. Details regarding the conditions under which the error occurred or                         |

|    which actions and input caused the error.                                                     |

----------------------------------------------------------------------------------------------------

 

 

----------------------------------------------------------------------------------------------------

|System environment                                                                                |

|    SAP Release..... 740                                                                          |

|    SAP Basis level 0010                                                                          |

|                                                                                                  |

|    Application server... CTSC005113289                                                           |

|    Network address...... 10.155.140.125                                                          |

|    Operating system... Windows NT                                                                |

|    Release.............. 6.3                                                                     |

|    Hardware type....... 4x AMD64 Level                                                           |

|    Character length..... 16 Bits                                                                 |

|    Pointer length........ 64 Bits                                                                |

|    Work process number... 11                                                                     |

|    Shortdump setting. full                                                                       |

|                                                                                                  |

|    Database server... CTSC005113289                                                              |

|    Database type..... MSSQL                                                                      |

|    Database name..... E91                                                                        |

|    Database user ID e91                                                                          |

|                                                                                                  |

|    Terminal..........                                                                            |

|                                                                                                  |

|    Character set C                                                                               |

|                                                                                                  |

|    SAP kernel....... 742                                                                         |

|    Created on....... Mar 24 2015 16:58:40                                                        |

|    Created at....... NT 6.1 7601 x86 MS VC++ 16.00                                               |

|    Database version SQL_Server_9.00                                                              |

|    Patch level....... 101                                                                        |

|    Patch text.......                                                                             |

|                                                                                                  |

|    Database............. MSSQL 9.00.2047 or higher                                               |

|    SAP database version. 742                                                                     |

|    Operating system... Windows NT 6.0, Windows NT 6.1, Windows NT 6.2, Windows NT                |

|     6.3                                                                                          |

|                                                                                                  |

|    Memory consumption                                                                            |

|    Roll.... 0                                                                                    |

|    EM...... 7221168                                                                              |

|    Heap.... 0                                                                                    |

|    Page.... 40960                                                                                |

|    MM used. 1125232                                                                              |

|    MM free. 724240                                                                               |

----------------------------------------------------------------------------------------------------

 

 

----------------------------------------------------------------------------------------------------

|User and Transaction                                                                              |

|    Client................. 000                                                                   |

|    User.................. DDIC                                                                   |

|    Language key.......... E                                                                      |

|    Transaction.........                                                                          |

|    Transaction ID...... 48BC95E5CDFCF1E180F6005056BA4CFE                                         |

|                                                                                                  |

|    EPP whole context ID...... 00000142004F00550050003100200020                                   |

|    EPP connection ID........ 00000000000000000000000000000000                                    |

|    EPP call counter......... 0                                                                   |

|                                                                                                  |

|    Program.............. /SCMB/CL_DF_DOCUMENT_TYPE=====CP                                        |

 

Regards,

Preetha Balan

Kit to stock process, triggered from EWM

Hi,

has anyone here ever managed to get a kit-to-stock process running? In general my process is working, I have a VAS order, an outbound delivery order and an inbound delivery. But both deliveries in EWM use the same BP. As this BP is a vendor, of course the outbound delivery order shows an error and does not create the outbound delivery in ERP. All settings I can think of are done, but still no success. Any pointers what I am missing?

Brgds

Juergen

Viewing all 1703 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>