Segment in SD & MM transactions

Hi
As we are using Derived Segment FAGL_DERIVE_SEGMENT (there is no segment assignment in PCtr master data i.e. segment identified with out PCtr also), the segment field is not coming in VA01, ME21N.
What to do to get the field segment in the above transactions.
Let me know if there is any other process do.
Please help me out
Thanks & Regards
Ramki

Hi Ramki,
I think you should report your inquiry in Materials Management Forum, there you will have the answer of MM experts. And also within SD Forum.
Best Regards,
Vanessa.

Similar Messages

Segment field in SD transaction Postings

Hi
As we are using Derived Segment FAGL_DERIVE_SEGMENT (there is no segment assignment in PCtr master data i.e. segment identified with out PCtr also), the segment field is not coming in VA01, ME21N.
What to do to get the field segment in the above transactions.
Let me know if there is any other process do.
Please help me out
Thanks & Regards
Ramki
Edited by: Ramki on Feb 11, 2009 11:46 AM

Thanks Paul
We are using the BAdI FAGL_DERIVE_SEGMENT, which means no assignment of segment to the PCtr. We have activated the account assignment objects in AA for PCtr only. There is no field Segment in Account assignment objects in AA. For reporting purpose we are using Evaluation group1 as Segment.
But in AA automatic postings like AIBU (CWIP Settlement line items) and AFAB system has to pick the segment field.
For this what I have to do? Please help me out
Thanks & Regards
Ramki
Edited by: Ramki on Jan 30, 2009 2:17 PM

Segment field in MM transaction Postings

Hi
As we are using Derived Segment FAGL_DERIVE_SEGMENT (there is no segment assignment in PCtr master data i.e. segment identified with out PCtr also), the segment field is not coming in VA01, ME21N.
What to do to get the field segment in the above transactions.
Let me know if there is any other process do.
Please help me out
Thanks & Regards
Ramki
Edited by: Ramki on Feb 11, 2009 11:47 AM

Thanks Paul
We are using the BAdI FAGL_DERIVE_SEGMENT, which means no assignment of segment to the PCtr. We have activated the account assignment objects in AA for PCtr only. There is no field Segment in Account assignment objects in AA. For reporting purpose we are using Evaluation group1 as Segment.
But in AA automatic postings like AIBU (CWIP Settlement line items) and AFAB system has to pick the segment field.
For this what I have to do? Please help me out
Thanks & Regards
Ramki
Edited by: Ramki on Jan 30, 2009 2:17 PM

Rollback segment for set transaction

there is way that i can setup a rollback segment for a spacific user or specific transction.
ALTER ROLLBACK SEGMENT big_rbs ONLINE;
SET TRANSACTION USE ROLLBACK SEGMENT big_rbs;
sql .....
commit;
ALTER ROLLBACK SEGMENT big_rbs OFFLINE;
the sql is going for about hour, i was woundering during that time can some else use this rollback segment. i just want this rbs to this user, how i can do that.
thanks

I guess i didn't clearify well. let say i created a rbs for specific tranction. before this transaction is start it will turn on this rbs and once this transaction is completed, it issue the command commit, and bring it back to this rbs offline. the question is durning this transaction does any other transaction can come and use this rbs instead of we have lot of other rbs.
I hope that you get my point.

TRANSACTION을 ROLLBACK SEGMENT에 할당하는 방법(SET TRANSACTION USE)

제품 : ORACLE SERVER
작성날짜 : 2003-04-04
TRANSACTION을 ROLLBACK SEGMENT에 할당하는 방법
==============================================
(SET TRANSACTION USE ROLLBACK SEGMENT)
Purpose
Batch job 등을 사용할 때 특별히 크게 만든 rollback segment를 사용하도록
할 수가 있다. transaction에 특정한 rbs를 지정하는 방법을 알아보자.
Explanation
Oracle은 다음과 같은 규칙에 의해 각 Transaction이 사용하는 Rollback
segment를 결정한다.
1. Active Transaction의 수가 가장 작은 Rollback Segment에 할당한다.
2. 만약 1의 조건에 만족하는 Rollback segment가 하나 이상이면, 가장
마지막에 할당된 rbs 다음의 rbs를 할당한다. 이것은 undo 기능을 더
오래 지속시키도록 해 준다.
그러나, Application이 큰 rollback segment가 필요하다면 위와 같이
자동적인 rollback segment의 할당이 아닌 Manual하게 특정 rollback
segment를 할당 가능하다.
다음의 방법을 사용한다.
1) 큰 rollback segment를 만든다. 큰 rollback segment 를 만들기
위해서는 rbs tablespace에 영역이 충분히 커야 하므로 필요할 경우
tablespace를 확장하는 작업을 한다.
<tablespace 확장>
$ sqlplus system/manager
sql> alter tablespace rbs add datafile '?/rbs1SID.dbf' size 100m;
<rollback segment 생성>
sql> create rollback segment big_rbs storage(initial 10m next 10m)
tablespace rbs;
sql> alter rollback segment big_rbs online;
2) Transaction 를 assign 한다.
<sqlplus>
SQL> set transaction use rollback segment big_rbs;
<pro*c>
exec sql commit work;
exec sql set transaction use rollback segment big_rbs;
<forms>
dbms_transaction.use_rollback_segment('big_rbs');
이와 같이 지정하면 이후에 commit 또는 rollback이 일어날 때까지
한 transaction에만 해당된다.

Transaction table in rollback segments

hi guys,
I have read the following, but am still having a little difficulty conceptualising. Would someone be kind enough to give me a very brief example?
thanks
For each rollback segment, Oracle maintains a transaction table--a list of all transactions that use the associated rollback segment and the rollback entries for each change performed by these transactions.

First of all, the statement is talking about old manual undo management using rollback segment.
If you check the preceding two paragraph of the statement then it's easier to understand,
It basically says, Rollback segment hold rollback entries of transaction. To make it easier to track transactions and undo entries, Oracle maintain a table to save such info.
Rollback segment , transaction and undo entries are one to many relationships.
Rollback Segment --< Transactions --< Undo Entries
http://download.oracle.com/docs/cd/B10501_01/server.920/a96524/b_deprec.htm
Contents of a Rollback Segment
Information in a rollback segment consists of several rollback entries. Among other information, a rollback entry includes block information (the file number and block ID corresponding to the data that was changed) and the data as it existed before an operation in a transaction. Oracle links rollback entries for the same transaction, so the entries can be found easily if necessary for transaction rollback.
Neither database users nor administrators can access or read rollback segments. Only Oracle can write to or read them. (They are owned by the user SYS, no matter which user creates them.)
How Rollback Entries Are Logged
Rollback entries change data blocks in the rollback segment, and Oracle records all changes to data blocks, including rollback entries, in the redo log. This second recording of the rollback information is very important for active transactions (not yet committed or rolled back) at the time of a system crash. If a system crash occurs, then Oracle automatically restores the rollback segment information, including the rollback entries for active transactions, as part of instance or media recovery. When recovery is complete, Oracle performs the actual rollbacks of transactions that had been neither committed nor rolled back at the time of the system crash.
When Rollback Information Is Required
For each rollback segment, Oracle maintains a transaction table--a list of all transactions that use the associated rollback segment and the rollback entries for each change performed by these transactions. Oracle uses the rollback entries in a rollback segment to perform a transaction rollback and to create read-consistent results for queries.

Transaction Identifier - ITL

The transaction id in the ITL contains the address of the undo segment number, slot number and wrap. I can infer that the undo segment number tells a transaction where to find a consistent read copy of the row(s) but cannot and do not want to guess what slot number and wrap are. I was reading an article on ITLs and the author says "When a transaction modifies a block (insert, delete or update) it records the transaction identifier in the ITL* of that datablock which is the part of variable header .... The transaction identifier contains the address of the rollback segment number (USN), slot number and wrap number.".
Link -> The article I was reading about this is here --> http://www.revealnet.com/newsletter/Transaction%20Management.htm.
Matt

Hi Matt,
The undo segment number, slot, and wrap (or sequence) make up a transaction id, and uniquely identify a transaction.
The undo segment number is just what it sounds like: The number of the undo segment being used. (Visible in dba_rollback_segs.segment_id)
The undo slot is the slot number in the undo segment header that the current transaction has reserved.
Finally, the wrap or sequence is simply a counter. Since transactions can recycle and reuse a specific undo segment number and slot combination, the wrap is simply incremented each time that specific slot in that specific segment is reused. It's just there to distinguish the transaction from the previous transaction that used the same slot previously.
Interesting bit of trivia, that's almost certainly no longer relevant. Before the days of automatic undo, when we all had to manually create and manage rollback segments, it was possible to "wear out" a rollback segment. The wrap is a 4 byte (32 bit) integer. So, if you ever used a slot in a rollback segment 2^32 (something over 4 billion) times, the rollback segment would need to be dropped, and a new one created. I just looked it up, it's an ORA-1558 that is raised when that happens. I just checked, and the error number/message still exists in 11g, though with Automatic Undo Management, I suspect you'll never see it occur.
-Mark

In KEPM error msg ' not all profitability segment can be processed'

Hi
PL HELP ME WITH THE FOLLOWING ERROR, when doing 'enter planning' in KEPM.
Message no. KG803
Diagnosis
You cannot maintain all of the profitability segments in the current transaction. This could be due to the following:
1. Errors occurred when characteristic values were derived for the profitability segments.
If this is the case, you can display the error messages under the menu option "Extras -> Error logs -> Derivation".
In the log , it says
Diagnosis
The characteristic "PRCTR" ("Profit Center") should be posted to Profitability Analysis (CO-PA). When the system checked the entries, it was established that the transferred characteristic value (" 1000 YB999") is not valid in CO-PA.
Thanks
kamala

Hi Kamala,
I would kindly ask you to check transaction OKEQN with your relevant planning version you are using in KEPM and where the above error occurs.
The system checks within derivation (where the error comes from) if the characteristic value is valid for a specific date set within the version (thus trans. OKEQN). If you have PRCTR '1000 102C511' not valid for the date set in the version within OKEQN, then this error message is justified, as the system realises that the PRCTR was not valid by that time.
Could you please check this? If the profit center is not valid for this date please adjust the date to a more recent one.
Best Regards,
Abhisek Patnaik

DiskUtility error: unable to bootstrap transaction group

I get this bootstrap error with a checksum mismatch but searching only found 1 other person with 'chksum mismatch' with 1 reply which was not of use.
"Unable to bootstrap transaction group 611: cksum mismatch
Unable to bootstrap transaction group 609: cksum mismatch"
MacBook Pro 13" early 2011, 10.7.2, Kingston 60 GB SSD as boot volume. FileVault full disk encryption is enabled.
I get this error when use Verify Disk when booted from the volume or even when I try to Repair Disk when I boot from a Lion flash drive or in target mode.
I also get the green OK messages at the end but when I Verify/Repair again, it still shows the same bootstrap errors. Why does this happen? Why doesn't DiskUtility fix it? Is it a bad error? Seems odd that it says OK at the end but still shows the errors.
Thanks.

I'm seeing this issue too. Disk repair wont fix it:
Verifying volume “Macintosh HD”
Checking storage systemChecking volume.
disk0s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
Logical Volume Group 2008965E-D094-4248-A616-CCADC11CCCFE spans 1 device
Logical Volume Group has a 16 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 1 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Unable to bootstrap transaction group 2149: inconsistent crosscheck
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Incorporate 0 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Unable to bootstrap transaction group 2148: inconsistent crosscheck
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Incorporate 0 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Unable to bootstrap transaction group 2147: inconsistent crosscheck
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Incorporate 0 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Unable to bootstrap transaction group 2146: inconsistent crosscheck
No valid commit checkpoint found
The volume 2008965E-D094-4248-A616-CCADC11CCCFE was found corrupt and needs to be repaired.
Error: Storage system verify or repair failed.

Rollback segment error

Hello experts,
My problem is as follows:
I need to perform a large transaction on one of my tables in my
database. I have to delete a large number of records using a
command as follows:
Delete from mytable where ordernumber like '2000%';
Each time i launch this command i have the following error:
ERROR at line 1:
ORA-01562: failed to extend rollback segment (id = 3)
ORA-01628: max # extents (30) reached for rollback segment R03
I know that i have a problem with my rollback segment. I have
thus created a large rollback segment so that my transaction can
use it.
I don't know how to tell my transaction use the large rollback
segment that i created.
(i know there is a command called set transation user rollback
segment large_rs1, i have tried it on sqlplus. it gives me
error: ORA-01453: SET TRANSACTION must be first statement of
transaction)
Please help
thanks in advance for a reply
Kind regards
Yogeeraj

First, you have to create a bigger rollback segment (i.e. RBBIG).
Then, before each query, you must type:
set transaction use rollback segment rbbig;
This will force the use of the specified rollback segment.
Hope this helps.

Exit /BTE in F110 transaction

Hi Experts,
   My requirement is when we complete the payment run process using F110. In Assignment field of the payment document I need to populate the "payment document numbercompany codefiscal year".
   I tried this using the substitution but the problem is when it call the substitution till that point of time document number is not created hence not able to update the same.
   Please let me know is there is any Badi's, exit or BTE's which triggered after the payment document is generated. so that i can update same in the assignment field.
Thanks in advance..

With a 'CALL CUSTOMER-FUNCTION' string search on a report (i.e.SAPF110V)
you can find an enhancement.
Through the package FIBP and SE80 you can find the BAdI's in thatpackage
(and maybe in that specific piece of
code you want to use).
Transaction Code - F110 Parameters
for Automatic Payment
Exit Name Description
FEDI0006 Function Exits for EDI-docs in
FI: Save IDCR Segments
FDTAX001 Enhancement to Transaction FDTA
(event after the download)
RFFOX003 Frame for user exit RFFOX003 (in
program RFFOM100)
FEDI0002 Function exits for EDI DOCS in FI
- Incoming pyt adv.notes
FEDI0003 Function exits for EDI docs in FI
- Save PEXR segments
FEDI0004 Function exits for EDI docs in FI
- particular events
RFFOX041 Framework for user exit RFFOX041
(in program RFFOBE_I)
RFFOX042 Framework for user exit RFFOX042
(in program RFFOBE_E)
RFFOX043 Framework for user exit RFFOX043
(in program RFFOBE_D)
RFFOX061 Frame for user exit RFFOX061 (in
program RFFOCH_P)
RFFOX062 Frame for user exit RFFOX062 (in
program RFFOCH_P)
RFFOX063 Frame for user exit RFFOX063 (in
program RFFOCH_P)
RFFOX064 Frame for user exit RFFOX064 (in
program RFFOCH_P)
RFFOX065 Frame for user exit RFFOX065 (in
program RFFOCH_P)
RFFOX066 Frame for user exit RFFOX066 (in
program RFFOCH_P)
RFFOX071 Frame for user exit RFFOX071 (in
program RFFOCH_U)
RFFOX072 Frame for user exit RFFOX072 (in
program RFFOCH_U)
RFFOX073 Frame for user exit RFFOX073 (in
program RFFOCH_U)
RFFOX074 Frame for user exit RFFOX074 (in
program RFFOCH_U)
RFFOX075 Frame for user exit RFFOX075 (in
program RFFOCH_U)
RFFOX081 Frame for user exit RFFOX081 (in
program RFFOF__T)
RFFOX082 Frame for user exit RFFOX082 (in
program RFFOF__T)
RFFOX100 Frame for user exit RFFOX100 (in
program RFFOUS_T)
RFFOX101 Frame for user exit RFFOX101 (in
program RFFOUS_T)
RFFOX102 Frame for user exit RFFOX102 (in
program RFFOUS_T)
RFFOX103 Frame for user exit RFFOX103 (in
program RFFOUS_T)
RFFOX104 user exit
RFFOX105 Frame for user exit RFFOX105 (in
program RFFOUS_T)
RFFOX200 Frame for user exit RFFOX200 (in
program RFFONZ_T)
RFFOX210 Frame for user exit RFFOX210 (in
program RFFOAU_T)
RFFOX211 Frame for user exit RFFOX211 (in
program RFFONZ_T)
RFFOX230 General program for user exit
RFFOX230 (in program RFFOJP_L)
RFFOX240 Enhancement for User Exit 240
(RFFOAT_P)
RFFOX250 Enhancement for User Exit 250
(RFFODK_E)
RFFOX901 Framework for user exit RFFOX901
(in program RFFOM100)
RFFOX902 Framework for user exit RFFOX902
(in program RFFOM100)

Profit Center Segment Change

Hi,
We have been using a segment on a profit center that is incorrect. There have been many postings to the profit center. I realize that I cannot change the segment directly in the master data of the profit center. What is the best way to approach this problem? Do I change the validity period of the existing profit center, create a new profit center with the correct segment and transfer the values?
Any suggestions are appreciated.
Thanks in advance,
Andy

Creating a new profit center with the correct segment is a good idea, but you will also have the need (I assume) to rectify the segment in the existing postings; else you have to have another means to consolidate the numbers into the correct segment for reporting purposes. The segment from the profit center gets defaulted in the transaction data, but using field status, you should also be able to change the incorrect segment in the existing transaction data (again, volume may be a constraint here!).
Please also see the following helpful messages in this forum on this topic.
How to change Field SEGMENT in Profit Centre Master
Modify segment in Profit Center
Segment in document posting

Segmentation fault when using snapshot isolation with Berkeley DB 6.1.19 and 5.1.29

Hello,
I have been experimenting with snapshot isolation with Berkeley DB, but I find that it frequently triggers a segmentation fault when write transactions are in progress. The following test program reliably demonstrates the problem in Linux using either 5.1.29 or 6.1.19.
https://anl.app.box.com/s/3qq2yiij2676cg3vkgik
Compilation instructions are at the top of the file. The test program creates a temporary directory in /tmp, opens a new environment with the DB_MULTIVERSION flag, and spawns 8 threads. Each thread performs 100 transactional put operations using DB_TXN_SNAPSHOT. The stack trace when the program crashes generally looks like this:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff7483700 (LWP 11871)]
0x00007ffff795e190 in __memp_fput ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
(gdb) where
#0 0x00007ffff795e190 in __memp_fput ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#1 0x00007ffff7883c30 in __bam_get_root ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#2 0x00007ffff7883dca in __bam_search ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#3 0x00007ffff7870246 in ?? () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#4 0x00007ffff787468f in ?? () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#5 0x00007ffff79099f4 in __dbc_iput ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#6 0x00007ffff7906c10 in __db_put ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#7 0x00007ffff79191eb in __db_put_pp ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#8 0x0000000000400f14 in thread_fn (foo=0x0)
    at ../tests/transactional-osd/bdb-snapshot-write.c:154
#9 0x00007ffff7bc4182 in start_thread (arg=0x7ffff7483700)
    at pthread_create.c:312
#10 0x00007ffff757f38d in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
I understand that this test program, with 8 concurrent (and deliberately conflicting) writers, is not an ideal use case for snapshot isolation, but this can be triggered in other scenarios as well.
You can disable snapshot isolation by toggling the value of the USE_SNAP #define near the top of the source, and the test program then runs fine without it.
Can someone help me to identify the problem?
many thanks,
-Phil

Hi Phil,
   We have taken a look at this in more detail and there was a bug in the code.   We have fixed the bug.     We will roll it into our next 6.1 release that we do.   If you would like an early patch that will go on top of 6.1.19, please email me at [email protected], reference this forum post and I can get a patch sent out to you.   It will be a .diff file that apply on the source code and then rebuild the library. Once again thanks for finding the issue, and providing a great test program which tremendously helped in getting this resolved.
thanks
mike

Manually Entering Segment

Hi,
I have created 4 segments:
SBU1
SBU2
SBU3
SBU4
I have created 3 Profit Centers
PC01
PC02
PC03
Now in the above scenario, the client wants
SBU1 >>> PC01 and PC02
SBU2 >>> PC01 and PC03
SBU3 >>> PC02 and PC03
SBU4 >>> PC01 / PC02 / PC03
If I do not maintain any segment in the above 3 Profit Centers Master Data, is it possible to manually enter the segment while posting an entry in the system?
NO NEW GENERAL LEDGER / DOCUMENT SPLITTING IS CONFIGURED IN THE CLIENT SYSTEM
Please assist on the same.

Hi
You have the choice to derive Segment
1. From Profit Center Master
2, Write your own logic in Badi FAGL_DERIVE_SEGMENT
3. Enter segment manually at each transaction.
Regards
Sanil Bhandari

Need to send multiple Loop-N1 Segments

Hi All,
I have created a BPEL process that takes a custom input XML document and creates and EDI 810 Invoice out of it.
The custom document has elements something like the below
<Invoice_Data>
<customer_Name>Customer Name</customer_Name>
<customer_Address>Customer Address</customer_Address>
<seller_Name>Seller Name</seller_Name>
<seller_Address>Seller Address</seller_Address>
</Invoice_Data>
The output needs to be something like this
<Transaction-810>
<Loop-N1>
<Segment-N1>
<Element-01>Customer Name</Element-01>
<Element-02>Customer Address</Element-02>
</Segment-N1>
</Loop-N1>
<Loop-N1>
<Segment-N1>
<Element-01>Seller Name</Element-01>
<Element-02>Seller Address</Element-02>
</Segment-N1>
</Loop-N1>
</Transaction-810>
I am using a transform activity but created the first N-1 Segment is easy but i do not understand how can i create two entries of that segment.
Please can someone help me with the xslt transform needed for this? An example would be really helpful

If the LoopN1 elements are not equal, you need to specify them separately in your template (this can't be done in design view as far as i know). The following works on your sample input:
<xsl:template match="/">
<Transaction-810>
<Loop-N1>
<Segment-N1>
<Element-01>
<xsl:value-of select="/Invoice_Data/customer_Name"/>
</Element-01>
<Element-02>
<xsl:value-of select="/Invoice_Data/customer_Address"/>
</Element-02>
</Segment-N1>
</Loop-N1>
<Loop-N1>
<Segment-N1>
<Element-01>
<xsl:value-of select="/Invoice_Data/seller_Name"/>
</Element-01>
<Element-02>
<xsl:value-of select="/Invoice_Data/seller_Address"/>
</Element-02>
</Segment-N1>
</Loop-N1>
</Transaction-810>
</xsl:template>

Segment in SD & MM transactions

Similar Messages

Maybe you are looking for