Invoice cancellation should not allow for closed periods

Dear All,
We will be closing the posting period for each quarter,and declare the sales figure.,what ever the invoices we have made should not be cancelled in that quarter.,i want the a check in the system that if any cancellation during this quarter which is closed ,should not allow to cancel the invoice.ofcourse the accounting document will not be generated as the posting period is closed but still the invoice is generated and blocked for accounting.i want the creation of billing document should be blocked.
i Know this can be achieved By defining new routine in VOFA and assign it in VTFL., but is there any standerd routine there which will solve my purpose or i hae to go for new routine.
REgards
Shakthi

Hello Shakthi,
In standard, there is note 180756.
Unfortunately the note 180756 just helps for billing creation, it is not useful for
billing cancellation.
The note 180756 suggests to develop a copy requirement routine checking
the periods.
But in VF11 copy requirement routine are not performed.
Unfortunately there is not a ready-to-use workaround.
In transaction VOFA is possible to define a "copy requirement" routine,
which is performed when the invoice is cancelled.
You could create a routine doing the necessary check, and put
it here.
Regards,
Alex

Similar Messages

Without result recording closing system should not allow for usage decesion

Hi
without result recording closing system should not allow for usage decision.I think it is possible through user status. Please tell the procedure .
Thanks and regards,
vairavan

Dear vairavan,
You can check for the authorisation object.I can't remember that authoriation object right now.But surely you can restrict that with authorisation object.
Anyone knows the authoristaion object.
Regards,
Sunil Patil

With out goods issue for order system should not allow for order confirmati

Dear all
with out goods issue system should not allow for order/operation confirmation.
how it is possible.
Regrads
Srinivas

Dear ,
In some cases we required to do confirmation or TECO without GI .
We can change it as per req using user exit
Regards,
Ishwar

QA32: Without going in Inspection lot stock screen system should not allow for UD

Hi
At the time of UD "without going in Inspection lot stock screen system should not allow to save the UD".
Please suggest how to restrict.
Regards
Ashish

Please go through the below link & with small changes you can fulfill your requirement using user profile
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/601c82e3-b743-2c10-dbb6-ed4c00167157?QuickLink=index&…

Delivery once billed should not allow again for billing

HI Friends,
Delivery once Billed should not allowed for billing again.
how to solve this, give the user exit if possible
Thanks & Regards
T.A.V

Hi,
Please ensure that the Copying Requirement routine 003 is assigned at the header for your billing and delivery type in transaction VTFL. Also set up 004 at the item level. I hope this will resolve the issue.
Regards,
Murali

TECO is not allowed without closing the inspection lot

Hello
I have implemented 03 & o4 inspection.
When I made TECO of Process Order system is allowed without making UD of inspection lot.
I required if the inspection lots are open of particular process order system should not allow for TECO.
Please suggest the solution.
Regards
Ashish R

Hi ,
Can you check in the Follow up action in spro whether you have defined FM QFOA_ORDER_TECHNICAL_COMPLETE and mark the After posting and Sync updating.
Check with your abaper with the below code -
CALL FUNCTION 'QFOA_ORDER_TECHNICAL_COMPLETE' "Follow-Up Action: Technically Complete PP Order with order category 40 ( AUFK-autyp= 40 )
EXPORTING
    i_qals =                    " qals
    i_qave =                    " qave
*   i_qapo =                    " qapo
IMPORTING
    e_subrc =                   " sy-subrc
TABLES
    e_protocol =                " rqevp
    . " QFOA_ORDER_TECHNICAL_COMPLETE
Otherwise , you can apply User Exit PPCO0007 in co02 or cor2
Regards
JH

Once payment received for bill system should not allow to cancel

Hi Experts ,
we have created commercial invoice and posted to fi document and payment received from party.but when we try to cancel the same billing document system allowing to cancel the document.So Client requirement is once payment received from party system it should not allow to cancel the billing document.
Please give your valuable suggestions on the same ...
regards...
MM

Hello,
In the Tx VOFA for the billing type to be cancelled(Ex F2), please
fill the field Copying Requirements(V_TVFK-GRBED_S) with '29'.
This routine prevents the cancellation of the billing documents which
have been cleared.
Regards,
Raghavendra YN

Residual payment should not allow more than Vendor Invoice

Hi,
Eg: Vendor has booked invoice 5000 INR, when user make payment through F-53 or F-58 through "Residual" payment user can pay more than invoice 5002 INR and below accounting entry is posting.
Bank Cr 5002 INR
To Vendor Dr 5000 INR (Invoice amount)
To Vendor Dr 02 INR Excess than invoice
Business requirement is system should not allow pay more than invoice amount. How to control suggestion would be appreciated.
I have done below settings for your understanding here system configuration.
1. OBA3: Under "Permitted Payment difference" zero for Gain , Loss , Amount, Percent & Adjust Discount By However "Permitted Payment Differences for Automatic write-Off(Function code AD)" zero.
2. OBA4: Cash discount per line item: Zero and Under "Permitted Payment difference" Revenues, Expense, Percent & Cash discount put Zero.
Regards,
Babu.

Hi Prashant,
I have restricted many fields to use through screen variant now user can not pay more than Invoice amount except through Residual payment process.
Client side management strongly says that they want to use Partial and Residual payment process options but user should not allow pay more than invoice amount.
If any solution please guide me.
Regards,
Babu.

Solution for Bug 13412084: RESTRICT PAYMENT: IT SHOULD NOT ALLOW PAYMENT BE

http://attiqahmed.wordpress.com/2012/03/20/solution-for-bug-13412084-restrict-payment-it-should-not-allow-payment-before-invoice-accrual/

hello sir Octavio
Im sorry.. I failed to tell you that our encoder of invoices is separate from the one who entry for payments.
Therefore, the encoder uses the invoices batches[(N) Invoices>Entry>Invoice Batches] whereas the Paymaster(the one who entered payments?) uses the Payments [Payments>Entry>Payments]
By the way your suggestion did work to disable the Pay in Full checkbox.. but i decided to get rid of the actions button for the encoder.. and another person will be handling the validation and create accounting having such access.
So what i wanted is that the paymaster wouldn't be able see among the LOV of invoices at the Payments Form if its not created accounting.
I wanna make sure that all invoices are created accounting.
thank you so much for the understanding..:-)
Emgee

Delivery is invoiced fully so system should not allow to create 2nd invoic

hi Expert,
my issue is, once invoice is created for delivery.
system should not allow user to create
second invoice for same delivery number.
where to check the confiurtion to stop such
behaviour
waiting for your reply
thanks
Alicia

Hi Alicia
In the copy control from delivery to invoice - T code VTFL
you can maintain the copy routines. try maintaining routine
3-- which is delivery reatled header
4-- which is delivery related item
also at item level copy control you may add the check in billign quantites
this would stop formc reating another invocie
Hope this helps
Thanks
Akasha

SRM PO failed: Indicator for GR-based invoice verification used not allowed

Hi Friends,
I have an issue with a specific PO failed to transfer from SRM to ECC. We are in ECS scenario, SRM 5.0 Service level 7.0. We are in process of SP upgrade but this issue occured in Production system which is still in old SP level(SP 7.0).
when I check the App Monitor, I am see the following errors: but the status shows Auto_Completed
1. PO: Indicator for GR-based invoice verification used not allowed
2. PO: Instance XXXXXXXXXX of object type PurchaseOrder could not be changed
3. PurchOrder XXXXXXXXXX: Purchase order still contains faulty items
4. PO XXXXXXXX: Indicator for GR-based invoice verification used not allowed
I can see the PO copied over to ECC. but status in SRM PO shows 'Error in Process'.
BBP_PD for object PO shows: Created, complete, ordered, In Transfer to Execute, Change was Transmitted as Inactive status. Transfer Failed shows Active, Document completed, created.
I checked BP Maintain for the vendor and PO and its no different than other POs and Vendors except Vendor had 'Goods Receipt based Invoice Verification' indicator checked in SRM.
I tried to simulate the same Material, Vendor with GR-IV indicator both on and off, it works fine. Ofcourse this is in Quality box with SP 15 level.
So, I am not sure if SP level upgrade might help it or not? If there are any other means to test, please advise.
thanks
Rao

I was wondering how I could liquidate the PO by either creating a new PO or ??.
What you could do to revive the PO in question is that after the upgrade, and after a round of background jobs run for CLEAN_REQREQ_UP and BBP_GET_STATUS_2, ask the buyer to make a dummy change to the PO (for example, change the description of the PO) and order again. This would trigger the transfer to the backend again. And hopefully this time, no error would occur.

ESS Business Package Error: Period type not allowed for profile ESS

Hi,
We are trying to configure the business package for Employee Self Service on Enterprise Portal 6.0. We followed this SDN contribution <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a">ESS doc guide</a>
So far we have successfully deployed the business packages and followed all the configurations that were pointed out in the doc guide. Unfortunately when we try to access the Employee Self-Service portal pages (Overview, Employee Search, etc), we encounter this error:
Critical Error:
Period type not allowed for profile ESS, error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Period type not allowed for profile ESS, error key: RFC_ERROR_SYSTEM_FAILURE
Any ideas on how to fix this issue?
Regards,
Jojo

Hi Jojo,
Have you solved the problem? If yes can you please help me even I am facing the same error.
this is very help full to me .
Thanks and Regards,
Shilpi.

System should not allow to delete PO line Item after GR/IR

Hi,
I am working on a SAP Retail Implementation project.
Currently the system is allowing us to delete the PO line items after doing GR or IR against that PO line item. But the clients requirement is that the system should not allow to delete PO line item after doing GR/IR.
We are using Account Assignment Category-N, Item Category-S.
Please let me know if you have the solution for this requirement.
Thanks in advance
Thanks & Regards,
Suresh

Hi,
Standard SAP will not allowed the PO to be deleted once it was GR done. The controlled is on the attributes of message to set as "E"
Message no. 06115
But if invoiced takes place, the is the point that PO can be deleted.
You have to do have a Enhancement using MM06E005, insert you logic here to check PO history tables like EKBE, then check if invoice " Q" (BEWTP) exist, the PO cannot be deleted once the user delete the PO line and SAVE it. Ask you developer to help you on the following coding.
Use MM06E005 and EXIT_SAPMM06E_012
IF SY-TCODE = 'ME22N'.
IF sy-ucomm = 'MESAVE' OR SY-UCOMM = 'YES'..
LOOP AT TEKPO.
IF TEKPO-LOEKZ = 'L'.
SELECT SINGLE BELNR FROM EKBE INTO BELNR1 WHERE EBELN = TEKPO-EBELN AND EBELP = TEKPO-EBELP AND BEWTP = 'E'.
IF SY-SUBRC = 0.
SELECT SINGLE BELNR FROM EKBE INTO BELNR2 WHERE EBELN = TEKPO-EBELN AND EBELP = TEKPO-EBELP AND BEWTP = 'Q'.
IF SY-SUBRC = 0.
Regards,

Limit PO Err Combination of GR/IR control not allowed for external services

Hi,
I am having a problem while replicating free text Limit PO's to R/3 in SRM 4.0 SP 13. The issue is while creating Free Text Limit SC with the "Confirmation and Invoice" option checked in, the PO's get created in SRM but fails while replicating to R/3 and in RZ20 errors as "Combination of GR/IR control not allowed for external services" although in vendor master i don't have check for the field "GR-Based Invoice Verification".
On the contrary while creating SC with the "Invoice Only" the PO is successfully replicated to R/3 with item category as B for limit orders.
Now i have noticed if i make changes in the vendor master data i.e. check the flag "GR-Based Invoice Verification" then the PO in my first scenario gets replicated successfully and also with respect to the second scenario but it gets replicated in both the scenarios as item category "D".
As far as SRM standard it should have ideally behave like the below:
Limit SC with GR AND Invoice -> item category D
Limit SC with invoice only -> item category B.
Now my question is why do my PO's fail in R/3 in the first scenario and also if i check the flag in vendor master for GR-Based Invoice verification then in the second scenario the item category is "D" instead of "B".
Thanks in Advance.
Best Regards
Anirban

Hi Georg,
We don't have any active implementation for the BADI BBP_PO_INBOUND_BADI.
Best Regards,
Anirban

Restrict the user should not allow to select No Excise entry tab in MIGO

Hi
how to restrict the user should not allow to select No Excise entry tab in MIGO
if the material Excisable user can bale to select the No Excise entry tab in MIGO . my requirement .... if the Pop come Please enter Excise Invoice number and Excise Invoice Date user should not change the No Excise how to restrict pls advise me
@sakhi

These are the options provided by SAP keeping in mind Indian Scenario. Sometimes, vendor forget to send excise invoice copy with the material, in such case, you can select 'Only Part I'.
Even if you have maintain vendor excise details & material excise details (By mistake) in J1ID, system will throw an error message, excise invoice value is zero. In such case, we can select option 'No excise entry'.
Your requirement can't be fulfilled in standard way. Even if you go for any Z- developement, you will lose the option.

Invoice cancellation should not allow for closed periods

Similar Messages

Maybe you are looking for