Thank you for sharing
Regards,
Alecsandra
Thank you for sharing
Regards,
Alecsandra
Then I don't understand. It works perfectly well for me, also with blanks in the folder name.
Hi Rableen,
After analysis of log shared found
SQL error 942:
C statement for table 'D010ENH ':
C SELECT * FROM "D010ENH" WHERE "IS_ENH"=:A0 AND "PROGRAMNAME"=:A1 ORDER BY "IS_ENH","PROGRAMNAME","VERSION","ENHNAME","ID"
C stmt_fetch() -> orc=942, 103=DBSL_ERR_DBOBJECT_UNKNOWN
B ***LOG BZA=> table D010ENH does not exist on database R/3 [dbtran 7778]
For the issue suggest you to follow SAP KBA 2148302 - Application tables do not exist on shadow Instance
Hope this will resolve your issue.
Regards,
Hi Rohit and Rupesh,
Thank you for the message.
We use MRP Groups so I looked into OPPR and under Availability Check, I see the checking rule maintained is PP.
I did look into user settings and under the general settings tab I see the checking rule is left blank.
We have been trying to figure out why are we facing committed quantity issue and even it seems safety stock was not considered as expected.
Do you think there the checking rule in MD04 ATP quantities affects or is it just for display?
Again,I appreciate your time and help.
Best,
Parth
Bruno
Qual status do processamento? Estava verde? Essa mensagem é depois de clicar em finalizar?
Se o status do processo não for verde o mesmo não é disparado e então o sistema limpa a tabela para nova leitura/entrada de dados.
Abraço
Eduardo Chagas
Hi,
Thanks for your fast reply.
The prerequisite is fulfilled in my situation, meaning that there is a record in 0105-1 with mu user.
Attached a screen shot of the gray insert button (marked in red). If it is there I believe there must be a way to activate it.
Regarding adding additional metadata attributes to documents. Are you familiar with a way to do it?
Step 1 : Entering datas at a crossing including the CATEGORY "Réel Analytique"
Step 2 : saving datas
Step 3 : refreshing the report
Step 4 : Changing the category member (Page Axis) for the parent of “Réel Analytique”
Please find a detailed step by step in attachement.
Thank you
Anthony
Hi,
Mr.Imran is correct, its due to authorization.
Thanks.
Hello Vinay,
can you please cross check:
http://wiki.scn.sap.com/wiki/display/BI/Installation+of+Precalculation+Server
Best regards
Carlos Behlau
Hi,
i have prepared a SP that will restrict unit price change on A/R invoice if price is different from delivery but this is not working any suggestion
IF @transaction_type IN ('A','U') AND @Object_type = '13'
BEGIN
--Declare @LineNumberDC varchar(10)
IF exists (Select a.ItemCode from INV1 a left join DLN1 b on a.BaseEntry = b.DocEntry and a.BaseLine = b.LineNum
WHERE a.DocEntry = @list_of_cols_val_tab_del group by a.ItemCode having SUM (a.Price) <> SUM (b.Price))
BEGIN
SET @error = 13
set @LineNumberDC = (Select Top 1 a.lineNum + 1 from INV1 a left join DLN1 b on a.BaseEntry =
b.DocEntry and a.BaseLine =b.LineNum where a.DocEntry = @list_of_cols_val_tab_del group by a.LineNum,a.LineTotal having
SUM (a.Price) <> SUM (b.Price) )
set @error_message = 'Amount is different from base document! (ROW: ' + @LineNumberDC + ')'
END
END
Thanks
Hi,
As mentioned by Rini, if you have made a call to the attachment method then only E-mail will have an attachment.
data : lv_sent_to_all TYPE boole_d,
lref_request TYPE REF TO cl_bcs,
lref_recipient TYPE REF TO if_recipient_bcs,
lref_document TYPE REF TO cl_document_bcs.
*--Create persistent send request
lref_request = cl_bcs=>create_persistent( ).
*----Create document from internal table with text
lref_document = cl_document_bcs=>create_document(
i_type = lc_htm " Document Type - HTML
i_text = lt_mailtxt " The E-Mail Body
i_subject = ls_maildata-obj_descr ). " The subject of E-Mail
*----Add document to send request
CALL METHOD lref_request->set_document( lref_document ).
lref_recipient = cl_cam_address_bcs=>create_internet_address( "abc@gmail.com" ). "Receivers Email
*----Add recipient with its respective attributes to send request
CALL METHOD lref_request->add_recipient
EXPORTING
i_recipient = lref_recipient.
**-- API to send emails
CALL METHOD lref_request->send(
RECEIVING
result = lv_sent_to_all ).
BR.
Hiii,
I am facing same isuue. I have done following settings and my issue get resolved-
1.go to SPAD
2. go to access method and select type G.
Thanks Unnikrishnan Sir, The Query Worked and our client is happy.
Good that a problem has been solved. You can mark the relevant responses as correct/helpful and close the thread.
Lo de "Fijar cuentas contables por" no es para el costeo sino para indicarle a SAP como elegir las cuentas contables para las operaciones de los artículos.
Sobre tu duda, yo te plantearía 3 alternativas de solución:
1. Si el método de costeo es Costo Promedio (por la info q proporcionas es lo más seguro), se me ocurre q crees un almacén nuevo y le actives la funcionalidad de Ubicaciones (si es q tu versión de SAP te lo permite). Enseguida, crear 1 ubicación por cada almacén existente en SAP. Posteriormente dar de baja todo el inventario y darlo de alta utilizando el almacén nuevo y eligiendo la ubicación que hayas creado por cada almacén para su respectivo stock. Previo al proceso de carga de inventario tienen que decidir qu costo de artículo van utilizar.
ESto has q tengas solo un almacén y el stock repartido en 3 ubicaciones, lo que hace q tal vez deban replantear ciertos procesos de captura ya que ahora deberán elegir la ubicación y no el almacen (predeterminar el almacén nuevo en todos los artículos). Además también en los reportes que tengas personalizados donde incluyas almacenes.
2. Cambiar los artículos a un método de costeo estándar, lo que permite fijar un costo único unico por almacén manualmente en los datos maestros del artículo, sininfluir el precio de compra en proveedores. Esto puede implicar ciertos aspectos fiscales y contables que deberías revisar junto con tus compañeros de Finanzas.
3. Crear una nueva empresa en la q tengas parametrizado lo que te comenta Felipe, sólo que implica cargar todo el inventario con el costo deseado, así como también tos los datos maestros u cuentas bancarias; y todos sus respectivos saldos iniciales (clientes, proveedores, bancos). Ademas de replicar todas las demás Parametrizaciones que tengas en la base de datos original.
CUalquiera de las 3 opciones es factible en SAP y representa dedicarle tiempo a análisis y pruebas antes de aplicarlo a productivo.
SAludos
JC.
Hi,
SAP might simply have forgotten to put this entry into one of the transports. Just try adding the entry into table T77RCF_PRM_PL.
Kind regards
Roman
Hi,
if you use the e-recruiting landscape with frontend backend separation and the user is locking on the frontend make sure that the RFC Connection from backend to frontend which is usually using the service user to create user accounts in case of manual data entry for external candidates has the correct password.
Kind Regards
Roman
Possible suspect: your application is 64-bit but the connectivity to the database is 32-bit?
Hi,
My suggestion
Given edition-based redefinition allows having multiple versions of PL/SQL objects, views and synonyms in a single schema, which makes it possible to perform upgrades of database applications with zero down time.
Edition-based redefinition allow to redefine the copied objects in isolation. The changes do not affect users of the application. One database must have at least one edition.
Rules
Created or upgraded Oracle Database starts with one edition named ora$base. The parent of the first edition created with a CREATEEDITION statement is ora$base. The statement CREATE EDITION e2 creates the edition e2 as the child of ora$base:
An editioned object is a schema object that has both an editionable type and an editions-enabled owner. An edition can have its own copy of an editioned object, in which case only the copy is visible to the edition. All objects editionable.
All PL/SQL object types:
A noneditioned object is a schema object that has a noneditionable type. An edition cannot have its own copy of a noneditioned object. A noneditioned object is identical in, and visible to, all editions
Example: Table
It would be a natural fit to add a new field at the model level. I would call this new property "Edition". This property would contains a List of Values (Edition names). I should be able to select one of the editions already present or create a new one.
Depending on the edition chosen by default at model level we would have access to this edition objects and all ora$base objects - not edited - and all object that have noneditionable type - as Table.
It would have when creating an new edition object that I am able to achieve an import or copy / paste from an object of a previous edition. The imported object should serve me as template, inspiration, and source.
Finally I should beableto take cognizancetheprevious editions éditionableobjectsby selecting aLOVproperty at object level.